- BO Team reportedly used the Log4Shell flaw to gain full control of a Russian developer’s network.
- The hackers hit Windows and Linux systems, stole private data, and reached source code and a code-signing server.
- Kaspersky believes the group prepared a supply-chain attack, but the company’s response stopped it first.
A cyber espionage group known as BO Team has broken into a Russian software developer’s network. The attack lasted several months. The hackers reached key systems and stole private information. They also entered the company’s software development area and its code-signing server.
Kaspersky believes the group was preparing a supply-chain attack. According to Kaspersky, the company’s response measures stopped the operation before it ended.
Hackers Spent Months Inside a Russian Developer’s Network
Kaspersky’s ICS CERT team shared the findings in a report published on November 5, 2026. The investigation began after the company reported strange network activity in June 2025. Kaspersky did not name the company. It only confirmed that the firm builds software for customers in Russia.
Researchers blamed the BO Team for the break-in. The group also goes by Black Owl, Hoody Hyena, and Lifting Zmiy. It is linked to cyber espionage and hacktivism, which means hacking to push a cause. The group has targeted Russian organizations before. Kaspersky’s report ties the break-in, the stolen data, and the code-signing server to this one group.
Russian-linked cyber activity has also drawn attention in the United States. In a separate case, U.S. officials said Russia targeted election systems in 21 states, highlighting concerns about cyber operations affecting government and critical digital infrastructure.
The attackers compromised both Windows and Linux systems during the intrusion. They first entered a Linux terminal server through an exposed SSH service. A terminal server lets many people connect to one main computer. SSH lets people log in to servers from far away. Think of it as an unlocked front door. Next, the hackers scanned the internal network. They wanted to identify the systems and services they could reach.
Log4Shell Flaw Opens the Door to Wider Access
Kaspersky found evidence that BO Team used CVE-2021-44228, widely known as Log4Shell. CVE-2021-44228 is the official tracking number for the flaw. This flaw sat inside a VMware vCenter Server running version 7.0.3. The attackers first failed to open the vCenter web page.
Later, they gained remote command-line access with root privileges. Remote command-line access lets a person type orders into a computer from far away. Root access works like holding the master key to a building. Kaspersky copied the exploit in a test environment. The test confirmed that the affected vCenter build had the flaw.
The attackers then took a private SSH key. A private key works like a secret password that proves who you are. They used it to connect to the hypervisor, which is the software that runs virtual computers. They also planted a backdoor disguised as a PostgreSQL component. A backdoor is a hidden way back into a system. The file carried the name “pgcache.” A scheduled task ran the script every hour. It worked like an alarm clock that woke the script on a fixed schedule. This lets the script fetch and run more harmful scripts.
The intrusion later spread across many parts of the network. It reached virtualization clusters, Windows and Linux servers, and backup systems. Virtualization clusters are groups of servers that share the work of running virtual computers. Backup systems store spare copies of company data. It also hit network equipment and security management infrastructure.
The group broke into a GitLab virtual machine too. A virtual machine is a computer that exists inside software. It opened source code repositories and took a private key. Source code is the written instructions that make software work. That key gave the attackers a path to the company’s Ansible orchestration system. Ansible helps manage many servers at once. Their access grew wider from there.
The hackers stole account credentials as well. Credentials are usernames and passwords. They also accessed Active Directory data, which holds account details for a company’s network. To avoid detection, they used legitimate system tools. According to Kaspersky, the attackers repeatedly deleted event logs and disguised harmful files. Event logs record what happens on a computer. Deleting them works like wiping footprints off the floor.
Code-Signing Server Raises Supply-Chain Fears
The code-signing server drew some of the biggest worries. The company used this server to sign compiled versions of its commercial software. Compiled versions are the finished files customers install. A signature works like a seal on a package. Kaspersky recovered evidence of blocked attempts to run harmful code on the server.
Researchers believe the attackers may have planned to inject malware (harmful software) into software builds before signing them. Another possible goal was stealing the company’s digital signature. The group could then sign harmful programs with it.
Either approach could have exposed the developer’s customers to more attacks. A supply-chain attack spreads harm through trusted software that reaches many users. However, Kaspersky stressed that it found signs of suspected preparation. It did not find a completed supply-chain attack.
After detecting the intrusion, the company took countermeasures. Those steps forced the attackers out of its network. BO Team then tried to steal employee credentials through a phishing campaign. Phishing means tricking people into handing over login details. The message posed as a mail-server account warning. The security team detected and blocked the attempt.
Kaspersky said the attackers did not encrypt or destroy the company’s files. Researchers believe the group lost access before reaching its suspected goal. Reports say the case highlights the risks software developers face. Attackers who reach internal build systems, source code, and digital signing tools can cause serious trouble.
Share this article
About the Author
Rebecca James is an IT consultant with forward thinking approach toward developing IT infrastructures of SMEs. She writes to engage with individuals and raise awareness of digital security, privacy, and better IT infrastructure.
More from Rebecca JamesRelated Posts
North Korean Hackers Use Deepfake CEOs in Fake Zoom Calls to Spread Malware
Arctic Wolf has identified 40 videos of the deepfakes used by the hackers themselves and suspected a...
Viral UK Privacy Claim Falsely Says Ofcom Will Collect Home Wi-Fi Passwords
A viral post says UK households must register their Wi-Fi passwords with the regulator Ofcom. The po...
UK Messenger Case Puts Encrypted Chat Privacy and Automated Image Checks Under Scrutiny
A British man was reportedly arrested after Facebook flagged an image he sent to his wife on Messeng...
York University Confirms Data Breach Exposing Personal Information Dating Back to 2007
York University indicates that an unauthorized person compromised personal information from digital ...
Hackers Use Hijacked WhatsApp Accounts to Spread Malware Disguised as Invoices
Cybersecurity agencies in Malaysia and Singapore warn about malware files sent through hacked WhatsA...
Apple Warns German Ministers and Lawmakers of Possible iPhone Spyware Attacks
Apple started sending spyware alerts to German ministers and lawmakers on October 29, and Germany...