IPCRIME | THE UNDERGROUND FILES | NOVEMBER 17, 2026
Kaspersky ICS CERT’s November 5 report describes a months-long intrusion at an unnamed Russian industrial-software developer that investigators attributed to the BO Team group. The historical case remains instructive in today’s supplier-attack coverage: a decades-old-style trust failure in infrastructure allowed attackers to approach a signing server capable of distributing trusted software updates. The researchers say the attempted malicious package injection was blocked.
The case was disclosed earlier this month
The affected company reportedly contacted Kaspersky in June 2025. Kaspersky’s November 5, 2026 publication reconstructs the compromise; this is not a claim that the first breach occurred November 17. The researchers describe an initial access path involving an externally accessible Linux service with password authentication and later likely exploitation of the Log4Shell vulnerability in a VMware vCenter environment.
A vulnerability that should already have been fixed
CVE-2021-44228, commonly known as Log4Shell, was publicly disclosed in 2021. Kaspersky reproduced exploitation against the same vCenter build in a lab but distinguishes that from direct proof of the exact attacker method. An old flaw can remain a serious issue where maintenance and asset inventories miss infrastructure components such as hypervisors.
The route into development operations
After obtaining privileged access, the intruder reached virtualization and Windows infrastructure, stole credentials, interfered with internal administration and eventually accessed infrastructure linked to code signing. Kaspersky describes backdoors, attempts to retain persistence and use of stolen email-signing material in further deception.
The key outcome: an attempted supply-chain attack was stopped
The security team observed and blocked attempts to alter software before signing. The public investigation does not establish that the threat actor succeeded in shipping maliciously signed updates to customers. That negative finding is as important as the documented damage: reaching a signing system does not prove a distribution-chain compromise was completed.
What defenders should review
Separate signing infrastructure from ordinary administration, limit where signing keys can be used, require approvals and auditable records for each release, review exposed management systems, and keep software patch inventories current. After a confirmed intrusion, certificates and access keys may require coordinated replacement, not merely updating the originally vulnerable server.
Sources and related research
Independent IPCRIME coverage based on published documents. This article is not an independent forensic investigation or a claim that every described potential impact occurred.
