All Articles

The week in one line: The breach kept arriving through someone else's system. A poisoned build tool seeded malicious LiteLLM packages into an estimated 2,500 organizations, a shipping partner's compromise exposed Valve's Steam hardware buyers, a data broker pulled services offline after activity on a vendor's servers, and North Korea's Lazarus group burned a Windows zero-day on defense and aerospace staff lured by fake job offers. The front door was rarely the way in; the dependency, the supplier, and the contractor were.

The week's most significant incidents

1. A poisoned build tool seeded malicious LiteLLM packages into an estimated 2,500 organizations

CloudSEK tied a threat actor it tracks as TeamPCP to an estimated 2,500 organizations and more than 434,000 CI/CD pipelines exposed through the widely used LiteLLM library. The attacker never touched LiteLLM directly. Instead it trojanized Aqua Security's Trivy scanner, which LiteLLM's own build pipeline pulled in automatically, and that inserted malicious code into LiteLLM versions 1.82.7 and 1.82.8 published to the Python Package Index. The packages were live for roughly 40 minutes, and that was enough. High-confidence matches reportedly reached the infrastructure of large enterprises across technology, finance, and manufacturing. The lesson for security leaders is that a dependency you trust can be poisoned two hops upstream: your build imported a scanner, and the scanner had been tampered with. Inventory what your pipelines install automatically, pin and verify build-tool versions, and treat any credential that passed through an affected pipeline as exposed. See the August 12 edition. Sources: SecurityWeek, The Hacker News.

2. Attackers exploited a VMware vCenter flaw to hold persistent access across 47 countries

CVE-2026-59310, a directory-traversal flaw in vCenter's Syslog service that Broadcom rated a maximum 9.8, was under active exploitation, with researchers at QUIRSO counting 361 victim IP addresses across 47 countries. The first connections to attacker infrastructure appeared on August 3, five days after the July 29 advisory. A suspected advanced-persistent-threat actor used the flaw to run code, then installed reverse SSH through a cron job so access survived reboots and console cleanup. Germany, the United States, Turkey, Iran, and France accounted for more than half the observed systems. Broadcom offered no workaround, which makes patching the only supported fix. vCenter sits at the center of the virtual estate, so a foothold there reaches the hypervisors under it. Patch to the fixed build, then hunt for unexpected cron entries and outbound SSH from vCenter during the exposure window rather than assuming the update evicted the intruder. See the August 13 edition. Sources: The Hacker News, Infosecurity Magazine.

3. Lazarus burned a Windows kernel zero-day on defense and aerospace staff

The only actively exploited flaw in Microsoft's August Patch Tuesday, CVE-2026-68820, was a use-after-free in afd.sys, the WinSock driver that handles network sockets for nearly every Windows application. Check Point attributed the exploitation to North Korea's Lazarus group as part of a fresh wave of Operation Dream Job, in which fake recruiter pitches lure engineers in defense, aerospace, and aviation into opening malicious archives. The exploit escalated a normal user session to SYSTEM, then deployed a rootkit that reportedly disabled dozens of security-monitoring channels. Microsoft rated the flaw 7.0 and patched it on August 11, a day after Check Point's disclosure, and it went into the CISA KEV catalog with an August 25 federal deadline. The takeaway is that severity scores understate a zero-day already in nation-state hands: apply the update, and treat unsolicited recruiting outreach to technical staff as a delivery channel worth briefing. See the August 11 edition. Sources: BleepingComputer, Check Point Research.

4. Water utility attacks spread to at least a dozen states, reported as Iran-linked

New Jersey and Alabama confirmed that water and wastewater facilities were hit in a campaign, reported as tied to Iran, that had now touched at least twelve US states and focused on internet-exposed operational technology. Minnesota was first to confirm, citing more than thirty affected systems, followed by Michigan, South Dakota, and Georgia, while other states warned utilities without confirming intrusions. The reported techniques went beyond data theft to configuration wiping, tampering with sensors, and disruption of operator interfaces. Utilities responded by shifting to manual operation, and no state reported a loss of water safety. The common weakness was familiar and fixable: control systems reachable from the public internet without adequate access control or segmentation. Take those interfaces off the internet, put them behind a VPN with phishing-resistant authentication, and rehearse the manual fallback before you need it. See the August 9 edition. Sources: SecurityWeek, SecurityWeek.

5. A Metabase zero-day scored a perfect ten and had already breached named companies

CVE-2026-72898 gave an unauthenticated attacker administrator access to the Metabase analytics platform through a SQL injection at the password-reset endpoint, and it carried a maximum CVSS of 10.0. It was exploited in the wild before the fix, with reporting naming victims including Framework, n8n, and Kilo Code, and CISA added it to the KEV catalog with an August 14 federal deadline. Metabase connects directly to the databases behind a business, so admin access to the console is a short path to the data it queries. Because the entry point is the password-reset flow, an exposed instance should be treated as potentially breached rather than merely vulnerable: patch to the fixed release, then review admin accounts, rotate database credentials the instance holds, and check reset-endpoint logs for abuse. See the August 11 edition. Sources: The Hacker News, CISA.

6. Third-party breaches hit Valve and LexisNexis while vishing targeted the biggest hedge funds

Three stories in one edition made the same point from different angles. Valve told buyers of Steam hardware that their data was stolen in a breach at shipping partner CEVA Logistics, so the exposure sat entirely in a vendor's environment. LexisNexis pulled its Diligence, Metabase API, and Newsdesk offline after unusual activity on third-party vendor servers, choosing availability loss over uncontrolled risk. And UNC6671, a group linked to BlackFile extortion, ran a voice-phishing campaign against hedge funds and private equity firms reported to include Point72, Millennium, Two Sigma, and Citadel, dialing help desks rather than exploiting a flaw. The connective tissue is that none of these turned on a software vulnerability in the victim's own stack. Map where your customer and corporate data physically lives with suppliers, script and test help-desk identity verification against caller manipulation, and rehearse the decision to take a service down. See the August 10 edition. Sources: BleepingComputer, BleepingComputer, BleepingComputer.

Also across the week

• The FBI and Korean National Police warned that Gunra ransomware was hitting critical infrastructure through old, unpatched Fortinet flaws (CVE-2024-55591 and CVE-2025-24472), a reminder that last year's known bugs are still this year's entry point. Infosecurity Magazine
• Cisco confirmed active exploitation of a Secure Firewall ASA and FTD flaw (CVE-2026-20349) that lets an unauthenticated attacker crash the device through the remote-access SSL VPN; it landed in the CISA KEV catalog. BleepingComputer
• N-able N-central servers were taken over after an incomplete earlier fix (CVE-2026-18577), extending the remote-monitoring-platform compromise carried over from the prior week. The Hacker News
• CERT Polska detailed how attackers pivoted from a compromised wind farm through a private cellular network into a combined-heat-and-power plant serving roughly 50,000 residents, reached a WAGO controller on default credentials, and stopped a steam turbine, the first observed OT compromise over a private APN. Help Net Security
• CISA warned that a critical Progress LoadMaster flaw was being actively exploited, and JetBrains TeamCity's unauthenticated remote code execution bug (CVE-2026-63077, CVSS 9.8) was added to the KEV catalog with a public proof-of-concept available. BleepingComputer
• Levi Strauss and Co. said social engineering led to corporate data theft from three employee computers, and defense supplier IEH Corporation disclosed a Microsoft 365 mailbox breach via phishing in an SEC filing. BleepingComputer
• North Carolina's ports operated manually after a cyberattack at Wilmington, Morehead City, and the Charlotte Inland Port, another operational-technology disruption in the same week as the water-sector campaign. BleepingComputer
• Connor Riley Moucka, the hacker behind the Snowflake customer-data extortion that touched 165 organizations and more than 100 million people, pleaded guilty in a US court. SecurityWeek
• Critical flaws were disclosed in Belgian eID software used by roughly two million people, a Gitea flaw let unauthenticated attackers read server files, and new research showed passkey-protected accounts could be hijacked via Google Password Manager. SecurityWeek

What to watch next week

FAQ

What was the biggest breach story of the week?
The LiteLLM supply chain compromise. A threat actor tracked as TeamPCP trojanized the Trivy build scanner, which LiteLLM's pipeline pulled in automatically, seeding malicious LiteLLM versions 1.82.7 and 1.82.8 that CloudSEK linked to an estimated 2,500 organizations and more than 434,000 CI/CD pipelines.

What was the common thread across the week's incidents?
The breach entered through someone else's system. LiteLLM came through a poisoned build tool, Valve's data left through shipping partner CEVA Logistics, LexisNexis traced activity to a third-party vendor, and Levi Strauss and IEH Corporation lost data to social engineering and phishing. The victim's own software flaw was often not the entry point.

Which vulnerabilities should we prioritize?
The actively exploited ones in the CISA KEV catalog: VMware vCenter (CVE-2026-59310), the Windows WinSock zero-day (CVE-2026-68820), Metabase (CVE-2026-72898), Cisco Secure Firewall ASA and FTD (CVE-2026-20349), N-able N-central (CVE-2026-18577), Progress LoadMaster, and JetBrains TeamCity (CVE-2026-63077). Patch these first, and treat any pre-patch exposure as an intrusion.

Why did the water utility attacks matter beyond the water sector?
They showed internet-exposed operational technology being manipulated for physical effect, not just data theft, across at least twelve states, with reporting tying the activity to Iran. The same pattern of exposed, unsegmented control systems applies to ports, energy, and manufacturing, all of which saw OT disruption in the same week.

What should security teams prioritize next week?
Audit and pin what CI/CD pipelines install automatically, clear the CISA KEV deadlines for Metabase and WinSock, hunt for persistence on any vCenter exposed before patching, take internet-facing OT interfaces offline, and brief technical staff on recruiter-themed lures and help-desk vishing.

More from the community: the CISO Platform Breach Intelligence hub, peer resources on supply chain security, vulnerability management, and third-party risk.

Corrections and takedown requests: CISO Platform is committed to accuracy and fairness. If any detail in this briefing is inaccurate, or if you represent an affected organization and would like a correction or removal, please contact us at pritha.aash@cisoplatform.com and we will review your request promptly.