Hunt: BO Team got from an SSH-exposed terminal server through Log4Shell on vCenter 7.0.3 to a developer's GitLab and code-signing server; check for an hourly 'pgcache' cron backdoor and nofrillsdns C2
- Patch debt: confirm no vCenter still loads a Log4j vulnerable to CVE-2021-44228; Kaspersky reproduced the exploit on the same vCenter build.
- Hypervisor persistence: look for
/etc/cron.hourly/pgcacheor other cron.hourly scripts that curl and run remote content; Kaspersky's sample (MD5346b04985ec6c5d107ba0ddf32fe7691) was timestomped to look like it dated from 2021. - Dormant C2: DNS lookups for
*.nofrillsdns.com, including hostnames that resolve to 127.0.0.1 until the operators switch them on. Also Global Socket (gsocket) use and ReverseSSH binaries. - Credential theft: lsass dumps via
comsvcs.dll, registry exports used to decrypt ntds.dit, a modified/usr/bin/nxnode-login, or files under/dev/shm/pulse-shm-*. - Infrastructure (per Kaspersky): VPN logins from 193.3.23[.]236 and 80.76.42[.]139.
- Build integrity: limit and log who can reach the signing server, require approvals for signing, and rotate DKIM and signing keys after any domain-wide compromise.
Sources: Kaspersky ICS CERT: Supply chain attack: BO Team in a software developer's infrastructure (Nov 5, 2026) · The Hacker News: BO Team exploits Log4Shell in VMware vCenter (Nov 16, 2026)