[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5NnFq4i3zrjyEgYMS1rr0CeC2qegIrYVQIlYx2d89hM":3},{"article":4,"iocs":55,"iocs_total":15,"watch_terms":83,"solutions":84,"lesson":174},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":32,"category":33,"article_tags":37},"028d5f1e-d2d5-470c-a674-13b875cdf1cc","BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server","bo-team-exploits-log4shell-in-vmware-vcenter-compromises-russian-firm-s-code-sig-1abe89","An investigation into suspicious activity within a Russian software developer's network has uncovered a months-long compromise of its development infrastructure and a software code-signing server. The activity, documented by Kaspersky's ICS CERT team after it was contacted by the affected developer in June 2025, has been attributed to a threat actor named BO Team (aka Black Owl, Hoody Hyena,","BO Team, a Ukrainian-origin threat actor, compromised a Russian software developer's infrastructure, including its code-signing server, by exploiting the Log4Shell vulnerability in VMware vCenter. The months-long intrusion, discovered in June 2025, aimed at cyber espionage and degrading Russia's military-industrial complex. The attackers established backdoors and deployed malware, with the compromise of the CI\u002FCD infrastructure indicating a potential supply chain attack.","BO Team exploited Log4Shell in VMware vCenter to compromise a Russian firm's code-signing server.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fbo-team-exploits-log4shell-in-vmware.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEgAvzoKykaMIpa6xx92YudipfUoEQnSkrE6p2CiWEVra5izr5GfuNQGOnfRuF0XV99v1IPRFe2Q6BF27UEq3BnWFS5onw97dt3hvszilQDANdtRdYi0_hTDOrKQvuwGn1mY_m-QTabV3jwWCNwXs_OizK2GLF3Eks5HJj5I7kbmA2IztruSBVjq5WOcxEM-\u002Fs1600\u002Flog4shell.jpg","2026-11-16T06:53:34+00:00","2026-11-16T08:00:26.111013+00:00",9,[17,20,22,24,26,29],{"name":18,"type":19},"BO Team","threat_actor",{"name":21,"type":19},"Black Owl",{"name":23,"type":19},"Hoody Hyena",{"name":25,"type":19},"Lifting Zmiy",{"name":27,"type":28},"VMware vCenter","product",{"name":30,"type":31},"Log4Shell","technology","6cbdd207-aaa1-4176-9534-e156b125e917",{"id":32,"icon":34,"name":35,"slug":36},null,"Nation-state","nation-state",[38,43,45,50],{"category":39},{"id":40,"icon":34,"name":41,"slug":42},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":44},{"id":32,"icon":34,"name":35,"slug":36},{"category":46},{"id":47,"icon":34,"name":48,"slug":49},"80544778-fabb-4dcd-aa35-17492e5dcf4f","Vulnerabilities","vulnerabilities",{"category":51},{"id":52,"icon":34,"name":53,"slug":54},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[56,60,62,65,69,71,75,78,80],{"type":57,"value":58,"context":59},"malware","ZeronetKit","Malware used by BO Team",{"type":57,"value":61,"context":59},"BrockenDoor",{"type":57,"value":63,"context":64},"Cobalt Strike","Tool used by BO Team",{"type":66,"value":67,"context":68},"cve","CVE-2021-44228","Log4Shell vulnerability exploited in VMware vCenter",{"type":57,"value":70,"context":64},"Mythic",{"type":72,"value":73,"context":74},"ip","80.76.42.139","Written defanged in the article text",{"type":76,"value":77,"context":74},"domain","lo1yaizaeghaevarood1ahtaichootaz.nofrillsdns.com",{"type":72,"value":79,"context":74},"193.3.23.236",{"type":76,"value":81,"context":82},"lo1yaizaeghaevarooD1ahtaichootae.nofrillsdns.com","Command and control domain for backdoor script",[27],{"controls":85,"vendors":173},[86,115,144],{"slug":87,"name":88,"problem":89,"products":90},"patch-management","Automated patch management","Known holes get closed in days, not months.",[91,99,107],{"vendor_slug":92,"vendor_name":93,"vendor_logo":94,"product_slug":95,"product_name":96,"url":97,"description":98},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"vendor_slug":100,"vendor_name":101,"vendor_logo":102,"product_slug":103,"product_name":104,"url":105,"description":106},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":108,"vendor_name":109,"vendor_logo":110,"product_slug":111,"product_name":112,"url":113,"description":114},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"slug":116,"name":117,"problem":118,"products":119},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",[120,128,136],{"vendor_slug":121,"vendor_name":122,"vendor_logo":123,"product_slug":124,"product_name":125,"url":126,"description":127},"bitdefender","Bitdefender","\u002Fvendor-logos\u002Fbitdefender.png","gravityzone","GravityZone","https:\u002F\u002Fwww.bitdefender.com\u002Fen-us\u002Fbusiness\u002Fgravityzone-platform\u002F","Endpoint protection, detection and response platform.",{"vendor_slug":129,"vendor_name":130,"vendor_logo":131,"product_slug":132,"product_name":133,"url":134,"description":135},"elastic","Elastic","\u002Fvendor-logos\u002Felastic.png","elastic-security","Elastic Security","https:\u002F\u002Fwww.elastic.co\u002Fsecurity","SIEM and endpoint security built on Elasticsearch, with open detection rules.",{"vendor_slug":137,"vendor_name":138,"vendor_logo":139,"product_slug":140,"product_name":141,"url":142,"description":143},"sophos","Sophos","\u002Fvendor-logos\u002Fsophos.png","sophos-endpoint","Sophos Endpoint","https:\u002F\u002Fwww.sophos.com\u002Fen-us\u002Fproducts\u002Fendpoint-security","Endpoint protection with Intercept X anti-ransomware technology and EDR.",{"slug":145,"name":146,"problem":147,"products":148},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",[149,157,165],{"vendor_slug":150,"vendor_name":151,"vendor_logo":152,"product_slug":153,"product_name":154,"url":155,"description":156},"threatlocker","ThreatLocker","\u002Fvendor-logos\u002Fthreatlocker.png","zero-trust-endpoint-firewall","Zero Trust Endpoint Firewall","https:\u002F\u002Fwww.threatlocker.com\u002Fcapabilities\u002Fzero-trust-endpoint-firewall","Centrally managed host firewall with device-level and dynamic access rules, to limit which machines can talk to each other.",{"vendor_slug":158,"vendor_name":159,"vendor_logo":160,"product_slug":161,"product_name":162,"url":163,"description":164},"illumio","Illumio","\u002Fvendor-logos\u002Fillumio.png","illumio-segmentation","Illumio Segmentation","https:\u002F\u002Fwww.illumio.com\u002Fillumio-segmentation","Maps traffic between workloads and enforces segmentation across data centre, cloud and endpoints.",{"vendor_slug":166,"vendor_name":167,"vendor_logo":168,"product_slug":169,"product_name":170,"url":171,"description":172},"akamai","Akamai","\u002Fvendor-logos\u002Fakamai.png","guardicore-segmentation","Akamai Guardicore Segmentation","https:\u002F\u002Fwww.akamai.com\u002Fproducts\u002Fakamai-guardicore-segmentation","Software-based microsegmentation with traffic visibility.",[],{"slug":175,"title":176,"body":177,"framework_refs":178,"framework_notes":184},"unpatched-log4shell-in-vmware-vcenter-opens-door-to-code-signing-compromise","Unpatched Log4Shell in VMware vCenter Opens Door to Code-Signing Compromise","BO Team exploited the Log4Shell vulnerability (CVE-2021-44228) in VMware vCenter — a flaw publicly disclosed and patched in December 2021 — to gain initial access to a Russian software developer's environment years after the patch was available. The attackers pivoted from the vulnerable vCenter instance to the organization's code-signing server and CI\u002FCD infrastructure, creating the conditions for a downstream supply chain attack against anyone trusting software signed with the compromised keys. This incident illustrates how a single unpatched internet-facing system can cascade into a catastrophic trust violation: software signed by a compromised key may be weaponized against end users or partner organizations without their knowledge. The months-long dwell time before discovery in June 2025 further amplifies the damage, allowing attackers to establish persistent backdoors and conduct sustained espionage.",[179,180,181,182,183],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded","NIS2 Article 21(2)(d)","MITRE ATT&CK T1195: Supply Chain Compromise",{"NIS2 Article 21(2)(d)":185,"NIST SP 800-53 SI-2: Flaw Remediation":186,"MITRE ATT&CK T1195: Supply Chain Compromise":187,"CIS Control 7: Continuous Vulnerability Management (v8)":188,"NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded":189},"This point requires security measures covering supply chain risks; the compromise of the code-signing and CI\u002FCD infrastructure directly endangered downstream software consumers and falls squarely within supply chain security obligations.","SI-2 requires timely identification and correction of information system flaws; enforcing this control would have mandated patching the Log4Shell vulnerability long before the intrusion occurred.","The attackers' access to the code-signing server and CI\u002FCD pipeline matches this technique, where adversaries tamper with software build or distribution processes to reach downstream victims.","This control requires organizations to continuously assess and remediate vulnerabilities; applying it would have identified the unpatched Log4Shell flaw in vCenter before attackers exploited it.","This category requires maintaining awareness of known vulnerabilities in deployed assets; a process fulfilling it would have flagged Log4j exposure in the VMware vCenter environment."]