Cleartext

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 4 topic areas, including: Polish intelligence warns hackers attacked water treatment control systems; DOJ says ransomware gang tapped into Russian government databases; MuddyWater hackers use Chaos ransomware as a decoy in attacks.

The Record (Recorded Future) · May 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Russian-linked attacks on Polish water treatment SCADA systems represent continued escalation of OT targeting in NATO-allied nations, reinforcing the need for CISOs with OT environments to prioritize ICS segmentation and monitoring.

📖 Read full article

TechCrunch Security · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The DOJ's revelations about ransomware gangs having access to Russian government databases illustrates the deep state-criminal nexus that makes attribution and deterrence harder, informing threat modeling for enterprise security programs.

📖 Read full article

BleepingComputer · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Iran's MuddyWater APT using false-flag ransomware via Microsoft Teams social engineering targeting US organizations means CISOs must ensure Teams security controls are hardened and IR teams can distinguish espionage from criminal ransomware.

📖 Read full article

The Record (Recorded Future) · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A China-linked supply chain compromise of a widely-used software tool distributed through official channels reinforces the need for CISOs to validate software integrity even from trusted vendor websites and maintain software bill of materials.

📖 Read full article

TechCrunch Security · May 06 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: A breach of an AI development tooling provider where API keys were exposed highlights third-party risk in the AI supply chain — CISOs should audit which AI dev platforms have access to sensitive credentials and enforce key rotation policies.

📖 Read full article

The Record (Recorded Future) · May 06 · Relevance: ████████░░ 8/10

Why it matters to CISOs: CISA's CI Fortify initiative signals a policy shift toward mandating isolation and offline operational capabilities for critical infrastructure, which will drive new resilience planning requirements and potentially new compliance obligations for affected sectors.

📖 Read full article

Risky Business News · May 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Post-Mythos AI regulation discussions will shape how enterprises can deploy frontier AI models and what security testing requirements may be imposed, directly affecting AI governance strategies CISOs are building now.

📖 Read full article

Cybersecurity Dive · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: NIST testing frontier AI models for cybersecurity risks could establish benchmarks that inform enterprise AI procurement decisions and shape future compliance requirements around AI deployment.

📖 Read full article

BleepingComputer · May 07 · Relevance: █████████░ 9/10

Why it matters to CISOs: A critical RCE zero-day in PAN-OS firewalls — core perimeter infrastructure — has been exploited by suspected state-sponsored actors for nearly a month with no patch available yet. CISOs running Palo Alto need immediate compensating controls and threat hunting.

📖 Read full article

Jordan: A critical remote code execution zero-day in PAN-OS firewalls. Actively exploited by suspected state-sponsored actors since April 9th. No patch. If you're running Palo Alto on your perimeter — and a lot of you are — that's your first call this morning.

Alex: Welcome to Cleartext. It's Thursday, May 7th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Today we're covering a lot of ground — that PAN-OS zero-day, Polish water treatment systems under attack, a DOJ revelation that reframes how we think about the Russian criminal-state nexus, Iran running a false-flag ransomware operation through Microsoft Teams, a supply chain hit on Daemon Tools, a breach at an AI tooling startup, and CISA's new CI Fortify initiative. Plus we'll get into what the post-Mythos AI regulation push means for how you're building your governance programs right now.

Alex: Let's start where we have to. Palo Alto, PAN-OS, unpatched RCE zero-day. Jordan, walk us through the exposure.

Jordan: Here's what we know. The vulnerability is critical severity. Remote code execution. It's been in active exploitation since approximately April 9th — that's nearly four weeks of adversary runway before public disclosure. Attribution points to suspected state-sponsored actors, which tells you this wasn't opportunistic. This was deliberate, targeted, and quiet. Palo Alto has not released a patch as of this morning.

Alex: The business risk here is straightforward and serious. Your firewall is not a secondary system. It is the perimeter. If you're running PAN-OS, you need compensating controls in place today — threat hunt your edge environments, review logs going back to April 9th, restrict management plane access if you haven't already. And brief your board. A state actor on your firewall for a month is a material risk conversation, not a technical footnote.

Jordan: Palo Alto will have guidance on mitigations. Implement them. Don't wait for the patch.

Alex: Now let's talk about what's happening in the OT and critical infrastructure space, because two stories this week connect in important ways. Polish intelligence confirmed attacks on water treatment control systems — SCADA environments — attributed broadly to intensified hostile cyber activity with specific emphasis on Russian Federation special services. This was happening across 2024 and 2025.

Jordan: Poland is a NATO frontline state. Attacks on water treatment infrastructure aren't just about disruption — they're about signaling. They're about demonstrating reach and creating psychological pressure on allied governments. The fact that attribution is hedged publicly doesn't mean the intelligence community doesn't know exactly who did this. It means they're managing escalation.

Alex: For CISOs with OT environments — and that includes utilities, manufacturing, healthcare systems with embedded industrial controls — this is a forcing function. ICS segmentation, OT-specific monitoring, and incident response playbooks that account for physical consequences. If your OT security posture is still basically "it's airgapped, we're fine," you are behind.

Jordan: And directly connected to that — CISA launched CI Fortify this week. The core premise is that critical infrastructure organizations need to be able to operate offline. Disconnected from third-party dependencies. No reliable telecom, no reliable internet. Proactively plan for that scenario.

Alex: This is a significant policy signal. CISA is essentially telling critical infrastructure operators: you cannot assume connectivity. Build for isolation. What this means practically is that resilience planning has to move from a theoretical tabletop exercise to an operational capability. And compliance obligations will follow. If you're in a critical infrastructure sector and you don't have an offline operational mode, start building the roadmap now before it becomes a mandate.

Jordan: The timing is not coincidental. You have the Polish water system attacks, ongoing OT targeting across NATO allies, and now a federal initiative explicitly designed to harden against exactly that threat vector. The policy is catching up to the threat.

Alex: Let's shift to the state-criminal nexus story, because the DOJ dropped something this week that deserves more attention than it's getting. US prosecutors revealed that a ransomware gang had access to Russian government databases — and used that access to help gang leaders dodge taxes and avoid military conscription.

Jordan: I want to be precise about what this tells us, because it's important for threat modeling. This isn't just "Russia tolerates cybercriminals." This is a documented, transactional, mutually beneficial relationship. The gang gets state protection and access to government systems. The state gets deniable offensive cyber capability and presumably a cut of the proceeds somewhere upstream. What it means for attribution is that when you're hit by a ransomware gang with Russian ties, you cannot cleanly separate criminal motivation from state interest. They are the same ecosystem.

Alex: From a threat modeling perspective, this should inform how you're scoping your adversary profiles. The line between financially motivated ransomware and state-sponsored espionage is genuinely blurred in the Russian context. Your IR retainer needs to know how to handle both, simultaneously.

Jordan: Now to Iran. MuddyWater — which is Iran's Ministry of Intelligence-linked APT — was caught this week running espionage operations disguised as Chaos ransomware attacks, targeting US organizations. Initial access was through Microsoft Teams social engineering.

Alex: Let's unpack the strategic intent here. The ransomware deployment is a false flag. The goal isn't ransom. The goal is intelligence collection — and making it look like criminal activity so that responders focus on containment and recovery instead of asking what was exfiltrated and by whom. That distinction matters enormously for your IR playbook.

Jordan: The Teams vector is worth flagging separately. Social engineering through Teams is increasingly effective because users treat it as a trusted internal channel. If your Teams environment allows external message initiation without friction, that's a control gap. Verify who external contacts are before they get any foothold. And make sure your IR team's initial triage includes the question: is this actually ransomware, or does it look like ransomware?

Alex: Supply chain story next — Daemon Tools. Kaspersky attributed a China-linked threat actor behind the compromise of the Daemon Tools official website, where trojanized installers were distributed. Thousands of users potentially backdoored.

Jordan: This is textbook supply chain tradecraft. You compromise the official distribution channel so that the software integrity question never gets asked. Users downloaded directly from the vendor site. The lesson is not that you should distrust every software vendor. The lesson is that your software procurement process needs integrity verification — hash checks, SBOM tracking — even for tools you've been using for years.

Alex: Especially for utility software that your IT and security teams use internally. Those tools run with elevated privileges and rarely get the same scrutiny as production systems. That's a gap adversaries understand well.

Jordan: Quick hit on the Braintrust breach. AI evaluation startup, Amazon cloud environment compromised, all customers told to rotate API keys immediately. The specific risk here is that Braintrust sits in AI development pipelines — which means the keys exposed potentially touch production AI systems and the data flowing through them.

Alex: This is the third-party AI supply chain risk materializing in real time. If your engineering teams are using AI dev tooling — evaluation platforms, fine-tuning infrastructure, anything in that stack — you need visibility into what credentials those platforms hold and a rotation policy that doesn't depend on the vendor telling you there's been a breach. Assume breach, rotate proactively.

Jordan: Now the AI governance picture. Two stories tie together here. NIST announced it will test frontier AI models from three major tech firms for cybersecurity risks, specifically spurred by Anthropic's Claude Mythos capabilities. And separately, the Risky Business team reported that the US government is actively weighing regulation of new AI model releases because of security implications.

Alex: Here's my read on this for CISOs. The policy environment around AI is moving fast, and it's moving specifically because of cybersecurity concerns — the ability of frontier models to assist with offensive operations. The debate about whether restricting frontier models actually achieves much when open models can do comparable things is legitimate. But that debate doesn't pause the regulatory process.

Jordan: What matters for enterprise AI governance right now is that the compliance landscape is in active formation. The frameworks you're building today — around AI procurement, acceptable use, access controls on AI systems — those need to be documented and auditable, because standards are coming and they will look backward at what you had in place.

Alex: The NIST testing program could become the basis for procurement benchmarks. Watch that closely.

Jordan: This week's theme is straightforward: your perimeter is under deliberate, sustained pressure from state and state-adjacent actors who are patient, well-resourced, and increasingly creative about initial access vectors — whether that's a Teams message, a trojanized installer, or an unpatched firewall sitting on your edge for four weeks.

Alex: And the policy response is accelerating — CI Fortify, NIST AI testing, AI regulation discussions. The compliance and resilience requirements coming out of this threat environment are going to be significant. The CISOs who are building those capabilities now, before the mandates land, are the ones who won't be scrambling when they do.

Jordan: Watch for PAN-OS patch release and indicators of compromise from Palo Alto. That's your immediate action item. Everything else is a planning conversation.

Alex: That's Cleartext for Thursday, May 7th. Show notes and links to every story we covered today are at cleartext.fm. If you find this useful, share it with a peer. We'll see you tomorrow.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-07.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 5 topic areas, including: CISA wants critical infrastructure to operate ‘weeks to months’ in isolation during conflict; Middle East Cyber Battle Field Broadens — Especially in UAE; Hackers compromise Daemon Tools in global supply-chain attack, researchers say.

CyberScoop · May 05 · Relevance: █████████░ 9/10

Why it matters to CISOs: CISA's CI Fortify initiative signals the US government is preparing for scenarios where nation-state cyber operations sever OT from IT — CISOs in critical infrastructure must now plan for sustained isolated operations and will face targeted assessments.

📖 Read full article

Dark Reading · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A tripling of breach attempts targeting UAE critical infrastructure amid the Iran conflict is a direct signal for CISOs at organizations with Middle East operations to elevate threat levels and review regional exposure.

📖 Read full article

The Record (Recorded Future) · May 06 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A supply-chain compromise of legitimate, signed software distributed from the vendor's official website is a nightmare scenario — CISOs need to audit whether DAEMON Tools is in their environment and review software provenance controls.

📖 Read full article

Dark Reading · May 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: When a security vendor's source code is breached, attackers can study detection logic and control mechanisms — CISOs using Trellix products should assess exposure and monitor for downstream exploitation of revealed internals.

📖 Read full article

The Record (Recorded Future) · May 05 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Australia's new Cyber Incident Review Board establishes a no-fault post-incident review model — CISOs at multinationals with Australian operations should prepare for potential scrutiny and leverage systemic findings to improve resilience.

📖 Read full article

BankInfoSecurity · May 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: For the first time skills and capabilities have overtaken headcount as the top CISO concern — this data point is directly useful for board-level workforce investment discussions and training budget justification.

📖 Read full article

BankInfoSecurity · May 06 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A $250-350M Cisco acquisition of Astrix Security validates non-human identity as a critical security category — CISOs evaluating NHI governance should consider how this consolidation may affect their vendor strategy and identity architecture.

📖 Read full article

BleepingComputer · May 06 · Relevance: ██████████ 10/10

Why it matters to CISOs: An actively exploited, unauthenticated RCE zero-day (CVSS 9.3) in PAN-OS firewalls is an emergency-level event — CISOs running Palo Alto infrastructure must assess exposure of User-ID Authentication Portals and apply mitigations immediately.

📖 Read full article

Jordan: If you're running Palo Alto firewalls with an internet-facing authentication portal, stop what you're doing. There is an actively exploited zero-day in PAN-OS right now. No patch. CVSS 9.3. Unauthenticated remote code execution. We'll tell you exactly what to do in the next sixty seconds.

Alex: Welcome to Cleartext. It's Wednesday, May 6th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we have a full slate. That PAN-OS zero-day is our lead. We've also got CISA's new CI Fortify initiative, which is one of the most significant posture shifts from the agency in years. Two supply chain compromises — one of them hits a security vendor's source code. The Middle East cyber battlefield is expanding fast. And we'll get into non-human identity, Australia's new cyber review board, and what the latest SANS survey tells us about where CISO priorities are actually shifting. Let's get into it.

Jordan: CVE-2026-0300. Buffer overflow in the PAN-OS User-ID Authentication Portal. CVSS 9.3. Unauthenticated RCE, confirmed exploitation in the wild, no patch available as of this morning. If your authentication portal is internet-facing, you are exposed right now. Palo Alto has published mitigation guidance — the immediate action is to disable or restrict access to the User-ID Authentication Portal from the internet if you haven't already. That is not optional at this point. Get your network team on the phone, confirm exposure status, and if you're using a managed service provider for your firewall ops, they should already be calling you. If they're not, that's a different conversation you need to have.

Alex: The board implication here is straightforward. Firewalls are perimeter. When perimeter becomes the attack surface, everything behind it is in scope. Document your exposure assessment and your mitigation steps today. If you're breached through this before a patch drops, you want a clear record that you acted on vendor guidance as soon as it was published. Watch for the patch. When it comes, treat it as emergency change control.

Jordan: Moving to the story I think has the longest strategic tail this week. CISA launched CI Fortify. The guidance is asking critical infrastructure operators to build the capability to operate in complete isolation — disconnected from IT networks and third-party vendors — for weeks to months. Not hours. Not days. Weeks to months. And they're backing this up with targeted assessments.

Alex: Let me translate that for anyone who needs to take this to their board. CISA is telling you, in writing, that the U.S. government believes nation-state actors — and the guidance specifically points to Chinese threat actors — are already embedded in operational systems. Not hypothetically. Already there. The agency is now asking operators to prove they can sustain operations if those IT and OT connections get severed in a conflict scenario. That is a fundamental shift in what resilience means for critical infrastructure.

Jordan: The OT-IT convergence trend of the last decade was about efficiency. CI Fortify is essentially asking you to architect for the opposite scenario — intentional, sustained segmentation under adversarial conditions. If your OT environment can't run for 30 days without calling home to a cloud vendor or a third-party patch server, you have a gap that CISA is now actively looking for. And with these targeted assessments coming, this isn't a future compliance problem. It's a current one.

Alex: Budget framing for this: the question you should be asking is what it costs to maintain isolated operational capability versus what it costs to go dark during a conflict. For most critical infrastructure operators, the latter is existential. This is a capital planning conversation, not a security team conversation.

Jordan: And tying directly to this theme — the Middle East. Breach attempts targeting UAE critical infrastructure tripled in recent weeks. As the Iran conflict has escalated, so has the cyber dimension, and the UAE is catching a significant share of that activity. If you have operations in the Gulf region — financial services, energy, logistics — your threat level needs to be elevated right now. This isn't ambient noise. Tripling of attempts in a few weeks against critical infrastructure sectors is a deliberate campaign pivot.

Alex: Review your regional exposure. Check your third-party relationships in that geography. And make sure your SOC team has the regional threat context they need to prioritize correctly.

Jordan: Two supply chain stories this week, and both deserve attention for different reasons. First, DAEMON Tools. Kaspersky found that attackers compromised the official DAEMON Tools website and swapped in trojanized installers — signed with legitimate developer certificates — starting April 8th. Thousands of infection attempts, at least a dozen confirmed compromises. Kaspersky attributes this to a Chinese-linked threat actor.

Alex: The signed certificate piece is what makes this operationally difficult. Your endpoint controls that validate signatures would have seen a clean bill of health. This is the supply chain problem in its purest form — the trust signal you rely on was weaponized at the source. Immediate action: audit your environment for DAEMON Tools installations, particularly anything installed after April 8th. If you find it, treat it as a potential compromise, not just a software issue.

Jordan: Second supply chain story hits closer to home for a lot of listeners. Trellix is investigating a breach of its source code repository. No confirmed exploitation yet, no code publicly released as of this morning, but that's almost beside the point.

Alex: Right. When a security vendor's source code is breached, the value to an attacker isn't necessarily releasing it publicly. It's studying it privately. Understanding where the detections are, how the logic works, where the blind spots are. If you're running Trellix products, you should be monitoring for any vendor communications, watching for anomalous behavior in those tools, and frankly thinking about detection diversity — whether you have enough independent visibility that a single vendor's logic being reverse-engineered doesn't create a coverage gap across your entire environment.

Jordan: Quick one on market structure. Cisco is reportedly in talks to acquire Astrix Security, a non-human identity startup, for somewhere between $250 and $350 million. That's a 25-plus percent premium over their last valuation.

Alex: Non-human identity is no longer an emerging category — it's arrived. Service accounts, API keys, OAuth tokens, machine credentials. The attack surface here has been growing for years while most organizations' governance hasn't kept pace. A Cisco acquisition at this price signals that NHI is being treated as core infrastructure-level security, not a specialty tool. If you don't have a current inventory of your non-human identities and a governance model around them, that gap is increasingly hard to justify.

Jordan: Two governance items to close out. Australia launched a Cyber Incident Review Board this week, explicitly modeled on the U.S. CSRB — which was, notably, recently disbanded here. The Australian board will conduct no-fault, post-incident reviews focused on systemic lessons rather than corporate culpability.

Alex: If you have Australian operations, get familiar with this body and its scope. The no-fault framing is designed to encourage honest participation, but participation in a government review of your incident is still a significant event. From a global governance standpoint, it's also worth noting: Australia is standing up the institutional infrastructure the U.S. just walked away from. That's a data point worth tracking.

Jordan: And the SANS survey finding that's useful for your next board conversation: skills and capability gaps have overtaken headcount as CISOs' top concern for the first time. Not vacancies — skills. The problem has shifted from not having enough people to not having people with the right capabilities.

Alex: This is a budget argument and a strategy argument simultaneously. Hiring your way out of a skills gap doesn't work if the talent pool doesn't have the skills you need. Training investment, capability development, retention of senior practitioners — these need to be line items that you can defend with data. That SANS finding is your data point.

Jordan: So what's the theme of this week?

Alex: Dependency. Every major story this week is fundamentally about what happens when something you trust fails or gets turned against you. Your firewall vendor's software. Your disk image utility's installer. Your security vendor's source code. Your OT network's IT connectivity. The thread running through all of it is that trusted dependencies — software, networks, vendors — are where the most sophisticated attackers are operating.

Jordan: The defense posture that follows from that is uncomfortable for a lot of organizations because it requires acknowledging that your control environment has assumptions baked into it that adversaries are actively testing. CI Fortify is the government making that explicit for critical infrastructure. The supply chain compromises are making it explicit for everyone else.

Alex: Next week, watch for a PAN-OS patch and whether exploitation has expanded beyond the initial targeting. Watch for any public release of the Trellix source code and how the vendor responds. And watch whether CISA's CI Fortify guidance triggers any mandatory compliance language — right now it's guidance, but the assessment program suggests that may not stay voluntary for long.

Jordan: That's Cleartext for Wednesday, May 6th. Show notes and links to every story we covered today are at cleartext.fm. If this was useful, share it with a peer. We'll be back tomorrow.

Alex: Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-06.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 5 topic areas, including: Australia launches cyber review board modeled on version disbanded in US; Everest Group Begins Leaking Alleged Liberty Mutual Data; Trellix discloses data breach after source code repository hack.

The Record (Recorded Future) · May 05 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Australia's new no-fault Cyber Incident Review Board signals a global trend toward systemic post-incident analysis; CISOs with APAC operations should prepare for potential participation in reviews and align incident response processes accordingly.

📖 Read full article

BankInfoSecurity · May 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A major insurer suffering a 108GB data leak including policyholder details has direct implications for any enterprise relying on cyber insurance—CISOs should assess third-party risk exposure and review whether their own policy data may be affected.

📖 Read full article

BleepingComputer · May 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A security vendor's own source code being breached raises serious supply chain trust questions; CISOs running Trellix products should assess whether compromised code could introduce vulnerabilities into their environments.

📖 Read full article

BankInfoSecurity · May 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Five Eyes joint guidance on agentic AI risks sets the baseline for how regulators and auditors will evaluate enterprise AI governance; CISOs deploying autonomous agents need to align with zero trust enforcement and human oversight recommendations now.

📖 Read full article

The Hacker News · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Given MOVEit's history as a major breach vector (2023 Cl0p campaign), any critical auth bypass in MOVEit products demands immediate CISO attention and accelerated patching of MFT infrastructure before exploitation begins.

📖 Read full article

BankInfoSecurity · May 05 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Cisco's potential $250M-$350M acquisition of Astrix validates non-human identity as a strategic security category; CISOs should evaluate how machine identity governance fits into their IAM roadmap, especially as this market consolidates.

📖 Read full article

TechCrunch Security · May 04 · Relevance: █████████░ 9/10

Why it matters to CISOs: An actively exploited Linux kernel vulnerability affecting every mainstream distribution since 2017 poses immediate risk to virtually all enterprise server and container infrastructure; CISOs must prioritize emergency patching of Linux fleets.

📖 Read full article

TechCrunch Security · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Mass exploitation of cPanel's authentication bypass affects web infrastructure broadly; CISOs should verify whether any business units or partners use cPanel-managed hosting and ensure immediate patching or mitigation.

📖 Read full article

Jordan: Your Linux servers. All of them. Every major distribution built since 2017. Being actively exploited, right now. That's where we're starting today.

Alex: Welcome to Cleartext. It's Tuesday, May 5th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we've got a full board. An actively exploited Linux kernel vulnerability that touches virtually every enterprise data center and container fleet on the planet. A ransomware gang leaking data from one of the largest insurers in the US. A security vendor's own source code gets breached. Five Eyes dropping joint guidance on agentic AI. A critical MOVEit patch that you do not want to sit on. Australia standing up a cyber review board modeled on the one the US just walked away from. And Cisco making a move in the non-human identity space. Let's get into it.

Jordan: So CopyFail. CISA confirmed active exploitation yesterday of a Linux kernel vulnerability that affects every mainstream distribution built since 2017. That's not hyperbole — that's the advisory. Successful exploitation gives an attacker root access. Full stop. If you are running Linux servers, containers, cloud workloads on standard distributions — and you are — this is your emergency patch event for the week. CISA has it on the Known Exploited Vulnerabilities catalog, which means federal agencies have a deadline. But honestly, so should you.

Alex: The operational calculus here is straightforward. You have a confirmed, active exploit chain targeting infrastructure that underpins most of enterprise computing. Your patching cadence does not matter this week. This supersedes it. Get your Linux fleet inventoried, get patches tested and deployed, and if you can't patch immediately, start thinking about compensating controls — network segmentation, privilege restrictions, enhanced monitoring on those hosts. Brief your team today.

Jordan: And while you're in that mode, cPanel. Separate issue, but same urgency window. Critical authentication bypass in cPanel and WHM, and we're already seeing mass exploitation. Thousands of sites compromised, attacks including ransomware deployment. If any part of your organization or your third-party web infrastructure runs cPanel-managed hosting, you need to know that today. This one has a narrower blast radius than CopyFail, but it's being actively weaponized at scale.

Alex: That brings us to a story that should make every CISO uncomfortable on multiple levels. Everest Group is now publicly leaking what they claim is 108 gigabytes of data from Liberty Mutual. Policyholder details. And they say the insurer failed to respond to their demands.

Jordan: The irony is almost too pointed. A cyber insurer, breached. Policyholder data — which could include details about the security posture and coverage limits of other enterprises — potentially in the hands of a ransomware gang. That's not a hypothetical threat chain. That's a live one.

Alex: There are two things I want CISOs to take from this. First: if you're a Liberty Mutual customer, you need to understand what data they hold about you, what your policy documents contain, and whether that information could inform targeting. Insurance applications are essentially detailed inventories of your weaknesses. Second, and more broadly — your cyber insurer is a third party. They hold sensitive information about you. How often are they in your third-party risk review cycle? For most organizations, the honest answer is not often enough.

Jordan: Liberty Mutual hasn't confirmed the breach scope yet, which is its own problem. When a ransomware gang is publishing your data and you're not communicating, you're losing the narrative entirely.

Alex: Now let's talk about a story that hits closer to home for a lot of us. Trellix disclosed a breach of a portion of its source code repository. Trellix, for context, is a major enterprise security vendor — XDR, endpoint, email security. If you're running Trellix in your environment, your question right now should be: what was in that code, and could a threat actor use it to identify vulnerabilities in the product before patches exist?

Jordan: This is the supply chain trust problem in its purest form. You deploy a security product specifically to defend your environment. That product's source code is now in unauthorized hands. The disclosure says "a portion" of the repository — which is the kind of qualifier that typically means we don't yet know what we don't know. Watch for any follow-on advisories from Trellix closely, and make sure your Trellix deployment is current on patches. If something new drops, you want zero lag time.

Alex: This is also a board conversation. Not necessarily this week, but the pattern — security vendors being breached — is something boards need to understand when they ask about your vendor stack. It's not just about the product. It's about trusting the vendor's own security posture.

Jordan: Switching gears. Five Eyes — the intelligence alliance covering the US, UK, Canada, Australia, and New Zealand — issued joint guidance yesterday on agentic AI. Autonomous AI systems. The kind that don't just answer questions but take actions across your environment.

Alex: And the timing is not coincidental. Enterprises are deploying these systems now, in many cases faster than governance can keep up. The Five Eyes guidance calls out three specific risk domains: identity — these agents need credentials and permissions, and managing that is genuinely hard. Visibility — autonomous agents create action chains that are difficult to audit after the fact. And control — the systems can outpace human decision-making by design.

Jordan: What they're recommending is essentially a zero trust framework applied to AI agents. Least privilege, continuous monitoring, and — this is the one that will create friction — meaningful human oversight checkpoints. The guidance stops short of mandating specifics, but here's what I'd tell CISOs: regulators and auditors will use this document. This is your baseline.

Alex: If you're in a regulated industry and you're deploying autonomous AI agents, you want to be able to demonstrate that you've read this guidance and that your deployment reflects it. Not because you have to today, but because you will have to, and "we weren't aware" is not a defensible position when it's a Five Eyes advisory.

Jordan: MOVEit. I know. I know. But yes, again. Progress Software patched a critical authentication bypass in MOVEit Automation. No confirmed active exploitation yet — emphasis on yet. We all know what happened in 2023. The Cl0p campaign that hit hundreds of organizations in a matter of weeks. MOVEit vulnerabilities do not stay unexploited for long.

Alex: Patch it now. Before the weekend. This is one of those cases where the history of the product tells you everything you need to know about threat actor interest. If you have MOVEit in your environment and you haven't patched by end of week, you're making a bet I wouldn't make.

Jordan: Now let's go to Australia, and this one matters strategically. Australia just launched a Cyber Incident Review Board — no-fault, post-incident reviews of significant attacks on government and industry, focused on systemic lessons. And yes, it's explicitly modeled on the US Cyber Safety Review Board that the current administration disbanded earlier this year.

Alex: The geopolitical read here is interesting. Other Five Eyes partners are essentially picking up governance frameworks the US has walked away from. For CISOs with APAC operations, this is practical: you may be asked to participate in one of these reviews. That means your incident documentation, your post-mortems, your timeline reconstruction all need to be ready for external scrutiny. The no-fault framing is important — this isn't litigation. But it does require transparency.

Jordan: And the bigger picture: as the US retreats from certain multilateral cyber governance structures, allies are filling the gap. That creates a patchwork of obligations for multinationals. If you operate across Five Eyes jurisdictions, you could be subject to review frameworks in multiple countries with different scope and processes. That's worth a conversation with your legal team now, not after an incident.

Alex: Quick note on the Cisco-Astrix story before we hit the outlook. Cisco is reportedly in talks to acquire Astrix Security — a non-human identity startup — for somewhere between 250 and 350 million dollars. Astrix focuses on service accounts, API keys, OAuth tokens. The messy, sprawling identity surface that most organizations have dramatically undercounted.

Jordan: The validation signal here is clear. Non-human identities now outnumber human identities in most enterprise environments by a significant factor. The market is consolidating. If you don't have a non-human identity governance program, you're behind the curve and the vendors are about to make it harder to ignore.

Alex: For the outlook this week, the through-line is pretty stark. CopyFail tells us active exploitation of foundational infrastructure is not slowing down. The Liberty Mutual breach tells us that the institutions we rely on to backstop cyber risk are themselves targets. Trellix tells us that security vendors are not exempt. And the Five Eyes AI guidance tells us that the governance frameworks for the next generation of enterprise risk are being written right now, whether we're at the table or not.

Jordan: What I'm watching: whether CopyFail spawns a secondary wave of intrusions we'll see documented over the next thirty to sixty days, and whether any of the Liberty Mutual policyholder data surfaces in ways that enable targeted attacks against named enterprises. Both of those have meaningful downstream consequences.

Alex: And on the governance side, I'll be watching how quickly APAC regulators begin operationalizing that AI guidance and whether the EU follows with something similar. The patchwork is growing.

Jordan: That's Cleartext for Tuesday, May 5th. Thanks for listening.

Alex: Show notes and links to everything we covered today are at cleartext.fm. We'll be back tomorrow.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-05.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 6 topic areas, including: Global Crackdown Arrests 276, Shuts 9 Crypto Scam Centers, Seizes $701M; Why data centers now belong on the critical infrastructure list; Risky Bulletin: DigiCert hacked with a malicious screensaver file.

The Hacker News · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: This unprecedented US-China-UAE coordinated law enforcement operation signals growing international willingness to collaborate on cybercrime—relevant for CISOs tracking BEC/fraud threat landscape and demonstrating that enforcement actions can meaningfully disrupt organized operations.

📖 Read full article

CyberScoop · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The push to designate data centers as critical infrastructure has direct implications for CISOs managing cloud-dependent operations—potential new regulatory requirements and heightened threat modeling expectations around physical and cyber resilience.

📖 Read full article

Risky Business News · May 04 · Relevance: █████████░ 9/10

Why it matters to CISOs: A breach of DigiCert—a foundational certificate authority for enterprise PKI and TLS—has immediate trust and supply chain implications; CISOs should assess certificate inventory exposure and monitor for any downstream impact on certificate validity.

📖 Read full article

BleepingComputer · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Given MOVEit's history as a mass-exploitation vector in 2023, any critical auth bypass in the MOVEit product family warrants immediate attention—CISOs should verify patching and assess whether automation instances are internet-exposed.

📖 Read full article

BankInfoSecurity · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A Cisco acquisition of Astrix at $250-350M validates non-human identity as a critical security category and signals platform consolidation CISOs should factor into identity program roadmaps and vendor strategy.

📖 Read full article

BankInfoSecurity · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Palo Alto's acquisition of Portkey for AI agent gateway capabilities signals that securing autonomous AI agents is becoming a mainstream platform play—CISOs deploying agentic AI need to plan for runtime security and identity controls over agent communications.

📖 Read full article

BleepingComputer · May 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Active exploitation of a Linux privilege escalation vulnerability with a public PoC demands immediate patching across Linux server fleets—this is a root-level compromise vector with rapid weaponization timeline.

📖 Read full article

The Hacker News · May 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Active exploitation of cPanel targeting government, military, and MSPs across multiple countries represents a supply-chain risk vector—CISOs with hosting or MSP dependencies should verify exposure and patch status immediately.

📖 Read full article

Jordan: A certificate authority just got compromised via a screensaver. Let that sink in for a moment. DigiCert — one of the foundational trust anchors for enterprise PKI globally — breached by what amounts to a 1990s attack vector. We'll get into what that means for every certificate your organization relies on.

Alex: Welcome to Cleartext. It's Monday, May 4th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we've got a dense one. DigiCert's breach and the trust chain implications that follow. MOVEit is back — yes, again — with a critical auth bypass. CISA is warning about active exploitation of a Linux privilege escalation flaw that went from proof-of-concept to weaponized in under 24 hours. We'll also talk about a landmark US-China-UAE law enforcement operation that seized $701 million in crypto fraud proceeds, why data centers may be heading toward critical infrastructure designation, and what Cisco and Palo Alto's latest acquisitions tell you about where the identity and AI security markets are heading. Let's get into it.

Jordan: Let's start with DigiCert, because this one has real teeth. The initial reporting indicates they were compromised through a malicious screensaver file — which, setting aside the almost darkly comic delivery mechanism, this is a serious supply chain trust event. DigiCert issues TLS certificates that sit underneath an enormous percentage of enterprise infrastructure. Authentication, encryption, code signing — all of it traces back to certificate authorities like DigiCert.

Alex: The immediate question for any CISO right now is: what's your certificate inventory look like, and do you have visibility into it? Most organizations don't. Certificate sprawl is a real problem — certificates issued years ago across dozens of teams, many of them untracked. If DigiCert's systems were compromised, the concern is whether any certificate issuance or private key material was touched. We don't have full details yet on scope, but the prudent move is to pull your DigiCert certificate inventory today and flag anything that may have been issued or renewed in a window proximate to this breach.

Jordan: The other story in that same briefing — Trellix also disclosed a separate breach. Two security vendors in the same news cycle. And two ransomware negotiators each sentenced to four years. That last item is actually significant. It signals that the DOJ is increasingly willing to go after intermediaries in the ransomware ecosystem, not just the actors themselves.

Alex: Which connects nicely to our next story. A coordinated operation involving the FBI, Chinese law enforcement, and Dubai Police just arrested 276 people, shut down nine cryptocurrency scam centers, and seized $701 million in fraud proceeds. This was primarily targeting pig butchering and crypto investment fraud schemes aimed at American victims.

Jordan: What makes this geopolitically notable is the US-China cooperation angle. These two countries don't coordinate on much right now. The fact that they found common ground on transnational financial crime — facilitated through the UAE as a neutral convening party — is meaningful. It doesn't signal a thaw in the broader relationship, but it does suggest there are narrow lanes where operational cooperation is possible when both sides see mutual benefit.

Alex: From a CISO perspective, BEC and fraud remain the top financial threat for most organizations. What this operation demonstrates is that enforcement can actually move the needle when it's coordinated at scale. It won't eliminate the threat, but it does raise the cost of operating these networks. The other takeaway is the UAE's emerging role as a serious cybercrime enforcement partner. Dubai is increasingly where these operations are being run out of, and the local authorities are apparently willing to act.

Jordan: Now, MOVEit. Progress Software has disclosed a critical authentication bypass vulnerability in MOVEit Automation. Patch immediately. That's the action item, and everything else is context.

Alex: The context matters though. In 2023, Cl0p's mass exploitation of MOVEit Transfer affected hundreds of organizations — healthcare systems, government agencies, financial institutions. It was one of the most consequential vulnerability exploitation campaigns in recent memory. The MOVEit brand carries that baggage. If you have MOVEit Automation instances in your environment — and many organizations do, because it's widely deployed for managed file transfer — your first question is whether they're internet-exposed. The second question is whether they're patched. Don't wait for your regular patch cycle on this one.

Jordan: Shifting to active exploitation. CISA confirmed that the 'Copy Fail' Linux vulnerability is being exploited in the wild — one day after researchers at Theori published a proof-of-concept. One day. That's the weaponization timeline you're working with in 2026.

Alex: This vulnerability allows privilege escalation to root on Linux systems. The exposure surface is significant — Linux underlies most cloud workloads, container infrastructure, and a large portion of on-premise server environments. The PoC was public, it was functional, and threat actors moved immediately. Your Linux patching cadence needs to reflect that reality. If you're still on a 30-day patch cycle for servers, this is a good week to have that conversation with your infrastructure team.

Jordan: And while we're on active exploitation — a previously unknown threat actor is targeting government and military entities in Southeast Asia, as well as MSPs and hosting providers across the Philippines, Laos, Canada, South Africa, and the US, using a critical cPanel vulnerability. Detected just two days ago by Ctrl-Alt-Intel. The MSP targeting is the piece that should get CISO attention, because that's a supply chain vector. If your managed service provider runs cPanel and hasn't patched, your environment could be downstream of that compromise.

Alex: Verify patch status with your MSPs. Get written confirmation. This is exactly the scenario where third-party risk management either pays off or doesn't.

Jordan: On the market side — Cisco is reportedly in talks to acquire Astrix Security for somewhere between $250 and $350 million. Astrix is a non-human identity player — API keys, service accounts, OAuth integrations, machine-to-machine credentials.

Alex: This validates something a lot of security leaders have been saying internally for a while: non-human identities are now the larger attack surface. The ratio of machine identities to human identities in a typical enterprise is already lopsided and it's getting worse. Cisco adding this capability to their identity portfolio is a signal that the major platforms are taking it seriously. If you haven't done a non-human identity audit recently — service accounts, API tokens, third-party OAuth grants — that's worth putting on the roadmap.

Jordan: And Palo Alto is acquiring Portkey to build out AI agent gateway capabilities. Runtime security, identity controls, and governance for autonomous AI agents. It's a narrower story but it's pointing at something real.

Alex: Every organization that's deploying agentic AI — and that number is growing fast — is dealing with the same problem. These agents have broad system access, they're communicating with external services, and the visibility into what they're actually doing is fragmented at best. The gateway concept is the right architectural response. Palo Alto is betting they can own that layer. For CISOs, the message is: if you're deploying AI agents without a security governance layer over their communications and identities, you have a blind spot that adversaries will eventually find.

Jordan: And that brings us to the data center critical infrastructure story, which is less of a news item and more of a policy trajectory worth tracking. The argument being made is that as AI deepens enterprise and national security dependence on cloud facilities, those physical facilities deserve the same regulatory designation as energy grids and telecommunications networks.

Alex: It's a reasonable argument. The problem is that critical infrastructure designation comes with regulatory obligations, and the cloud providers are going to push back hard on anything that creates new compliance surface for them. But for CISOs, the more immediate implication is threat modeling. If you're running AI workloads in cloud data centers and those facilities become higher-priority targets for nation-state actors, your resilience planning needs to account for that. Redundancy, failover, and supply chain concentration risk all come into focus.

Jordan: This week's through-line is actually pretty clear. The perimeter is gone, the trust model is broken, and everything is moving faster — breach to exploitation, patch to weaponization, AI deployment to attack surface. The DigiCert story is a reminder that trust anchors themselves can be compromised. Copy Fail going from PoC to active exploitation in 24 hours is a reminder that your response window has effectively shrunk to hours, not days.

Alex: And the acquisition activity from Cisco and Palo Alto tells you where the industry thinks the gaps are: non-human identity and AI agent governance. Both of those should be on your H2 planning radar if they aren't already. The organizations that build governance frameworks around machine credentials and AI agent behavior now will be ahead of both the threat curve and the regulatory curve.

Jordan: Busy Monday. Lots to action on.

Alex: That's Cleartext for May 4th, 2026. If this was useful, share it with a peer who needs it. We're back tomorrow. Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-04.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 18 stories across 6 topic areas, including: 76% of All Crypto Stolen in 2026 Is Now in North Korea; BlueNoroff Uses Fake Zoom Calls to Turn Victims Into Attack Lures; Chinese National Extradited Over Silk Typhoon Cyber Campaign.

Dark Reading · May 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: North Korea's dominance in crypto theft — and its use of AI-assisted social engineering — represents a material financial threat to any organization holding or managing digital assets. CISOs in fintech and crypto must treat DPRK as a persistent, well-resourced adversary.

📖 Read full article

Dark Reading · Apr 28 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: BlueNoroff's use of stolen victim videos and AI-generated avatars for fake Zoom calls represents a new tier of social engineering sophistication; security awareness training must evolve to address deepfake video calls targeting executives.

📖 Read full article

Infosecurity Magazine · Apr 28 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The extradition of an alleged Silk Typhoon member signals escalating US-China cyber tensions and reinforces that state-sponsored espionage campaigns targeting US organizations are being actively prosecuted.

📖 Read full article

The Hacker News · May 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A new China-aligned espionage campaign targeting government, defense, and NATO member states demonstrates persistent strategic cyber operations; organizations in targeted sectors should review their threat models for Chinese APT activity.

📖 Read full article

CyberScoop · Apr 30 · Relevance: █████████░ 9/10

Why it matters to CISOs: AI agents operating autonomously in production environments create a fundamentally new identity and access management challenge; CISOs must establish governance frameworks for non-human autonomous identities before agent sprawl outpaces controls.

📖 Read full article

BleepingComputer · May 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Insider threat from trusted security professionals is the nightmare scenario — two former incident responders at Sygnia and DigitalMint weaponized their access and knowledge. CISOs must enforce rigorous vetting and monitoring of third-party IR partners and internal security staff.

📖 Read full article

The Hacker News · May 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A security vendor's source code breach is a supply chain risk for every customer running their products — CISOs using Trellix should assess whether the exposed code could reveal exploitable weaknesses in their deployed defenses.

📖 Read full article

Infosecurity Magazine · Apr 28 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Medtronic's breach by ShinyHunters — with claims of millions of records accessed — highlights ongoing healthcare sector targeting and the particular risk to medical device manufacturers holding patient data.

📖 Read full article

The Hacker News · Apr 30 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Compromise of widely used open-source packages like PyTorch Lightning underscores the urgency of software composition analysis and CI/CD pipeline security — any team running ML workloads is potentially impacted.

📖 Read full article

CyberScoop · Apr 30 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Cordial Spider and Snarky Spider are executing rapid SaaS-focused extortion using voice phishing and SSO abuse — CISOs need to ensure helpdesk identity verification, MFA hardening, and SaaS DLP controls can withstand these accelerated attack patterns.

📖 Read full article

CyberScoop · May 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Five Eyes guidance on AI agent deployment signals regulatory direction; CISOs deploying agentic AI should benchmark their controls against this framework now before it becomes a compliance expectation.

📖 Read full article

The Record (Recorded Future) · May 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The NCSC warning validates what CISOs are experiencing: AI-accelerated vulnerability discovery is compressing patching windows and demanding a shift from periodic patch cycles to continuous vulnerability management.

📖 Read full article

CyberScoop · Apr 30 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Another 45-day Section 702 extension creates ongoing uncertainty for CISOs managing data governance programs that intersect with government data requests and intelligence sharing frameworks.

📖 Read full article

BankInfoSecurity · May 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Palo Alto's Portkey acquisition signals that AI agent governance is becoming a mainstream security product category — CISOs should evaluate whether centralized AI agent gateway controls fit their architecture as agentic AI adoption accelerates.

📖 Read full article

BankInfoSecurity · May 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Cisco's potential $250-350M acquisition of Astrix Security validates non-human identity management as a critical enterprise security category — reinforcing the week's theme that machine and agent identity is the next frontier.

📖 Read full article

VentureBeat Security · Apr 30 · Relevance: █████████░ 9/10

Why it matters to CISOs: Six research teams demonstrated that AI coding agents hold production credentials and authenticate without human sessions — this is an IAM blind spot that existing PAM and IdP tooling doesn't cover. CISOs need to audit what credentials their AI tools hold today.

📖 Read full article

Help Net Security · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: cPanel manages millions of websites globally; this auth bypass was exploited in the wild since at least February, months before a patch. CISOs with web hosting dependencies need to verify patching status immediately and assess exposure.

📖 Read full article

BleepingComputer · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A nine-year-old local privilege escalation flaw affecting virtually every Linux distribution since 2017 with a public PoC demands immediate patching across data center, cloud, and container environments. The fact it was found by AI underscores the 'patch wave' threat.

📖 Read full article

Jordan: Seventy-six percent. That's the number you need to carry into your Monday morning. Three out of every four dollars stolen in crypto globally this year went to North Korea. And they're not slowing down — they're using AI to do it faster. That's the geopolitical reality underneath what was otherwise a very busy week across breaches, vulnerabilities, and a governance story that I think most CISOs still haven't fully processed. We'll get into all of it.

Alex: Welcome to Cleartext. It's Saturday, May 2nd, 2026. I'm Alex Chen, joined as always by Jordan Reeves. If you had a real week and the news cycle got away from you, this is the episode you need. We're going to tell you what actually mattered, what connects, and what you need to be thinking about heading into next week. Here's how we're organizing it today: we're going to start with the geopolitical picture, because frankly it was dominant. Then we're moving into what I think is the sleeper story of the week — AI agents and the identity crisis they're creating. Third, we've got a breach cluster that has a disturbing common thread. And we'll close with vulnerabilities, because the patch queue is not getting shorter. Let's go.

Jordan: So let's talk about North Korea, because the seventy-six percent figure from Dark Reading is not a statistic you footnote — it's a threat brief. Kim Jong-un's cyber apparatus is running what is effectively a state-sponsored hedge fund that steals its capital. They're doing this on a weekly cadence now. And the BlueNoroff story from Monday adds the operational detail that should keep your security awareness team up at night: they're using stolen victim videos and AI-generated avatars to run fake Zoom calls targeting crypto executives. Let that sit for a second. Your counterpart at another firm gets compromised. Their likeness gets harvested. Now it's being used to socially engineer your team in a meeting that looks completely legitimate.

Alex: The "victim becomes lure" pattern is particularly nasty from an incident response standpoint. You remediate the breach, you notify the affected executive, and you think you're done — but their identity has now been weaponized against your organization and potentially dozens of others. The standard awareness training framework of "watch for suspicious links" doesn't address a deepfake video call from a face your executives actually recognize and trust.

Jordan: And then you layer in the Silk Typhoon extradition — a Chinese national pulled out of Italy and brought to the US for MSS-directed hacking that included COVID-19 research theft. That case covers 2020 to 2021, so it's a long tail on prosecution. But the signal it sends is that the US is willing to play a long game on attribution and extradition, even under diplomatic pressure. And Trend Micro dropped a new China-aligned campaign this week — SHADOW-EARTH-053 — hitting government and defense targets across Asia and at least one NATO member state, plus journalists and activists.

Alex: So the geopolitical picture this week is really two parallel tracks. North Korea is running financially motivated operations at scale, with AI acceleration, and with a targeting profile that now extends beyond pure crypto firms to anyone with digital assets or exposure to the space. China is running strategic espionage — governments, defense contractors, NATO adjacency, dissidents. Different goals, different TTPs, but both operating with increasing sophistication and both using AI as a force multiplier. For CISOs in financial services, fintech, or any organization managing digital assets, DPRK is not a background noise threat anymore. It's a named adversary that you should have in your threat model by name.

Jordan: Now let's pivot to what I think is the most structurally important story of the week, and it got somewhat buried under the breach headlines. CyberScoop ran a piece Wednesday on AI agents and identity, and it connects to about four other things that happened this week in ways that should worry you. The core problem: AI agents are being deployed into production environments with broad system access, and nobody has solved the identity layer for them. They're not human users. They don't authenticate through your IdP the way your employees do. They're not covered by your PAM policies. And they're already inside critical infrastructure.

Alex: CISA, NSA, and the Five Eyes partners published joint guidance on this Friday — which tells you the regulatory direction this is heading. When you get a joint advisory from that coalition, you're looking at what becomes a compliance expectation inside of eighteen months, maybe sooner. The guidance essentially confirms what the CyberScoop piece laid out: most organizations are granting agents far more access than they can safely monitor or control.

Jordan: And then there's the VentureBeat piece on AI coding agents — Claude Code, Copilot, Codex — where six independent research teams all reached the same finding through different exploits. Every single attack went for the credential, not the model. BeyondTrust showed a crafted GitHub branch name could steal Codex's OAuth token in cleartext. OpenAI rated it Critical P1. Claude Code leaked on npm. And Anthropic's own model was found to silently ignore deny rules after fifty subcommands — meaning your guardrails have a cliff edge built into them that nobody disclosed.

Alex: The through-line here is that your AI tools are holding production credentials and authenticating without human sessions, and your existing PAM and IdP tooling almost certainly has no visibility into that. This is an IAM blind spot that is not theoretical. The exploits are real, they're documented, and the PoCs exist. If your organization has deployed any AI coding assistant or agentic tool with access to production systems or code repositories, you need to audit what credentials those tools hold. This week, not next quarter.

Jordan: The M&A activity this week validates that this is a real product gap, not just a research problem. Palo Alto is acquiring Portkey to build an AI agent communications gateway. Cisco is reportedly in talks to buy Astrix Security for up to three-fifty — that's a non-human identity management play. When two of the largest security platforms in the world are spending that kind of money in the same week on the same problem space, the market is telling you something about where the risk is concentrating.

Alex: And the NCSC in the UK issued a warning this week about what they're calling a looming patch wave — AI is accelerating vulnerability discovery by both defenders and attackers, and the traditional patching cycle can't keep up. That warning was validated in real time this same week by the Copy Fail Linux vulnerability, which was discovered by an AI-equipped researcher at Theori, dropped with a ten-line public PoC, and affects every Linux kernel since 2017. Root access. Public exploit. Patch your Linux infrastructure before Monday.

Jordan: The cPanel zero-day is in the same category. CVE-2026-41940, critical auth bypass, exploited in the wild since at least February — months before anyone disclosed it. CISA added it to KEV Friday with a patch deadline of Sunday. If you have web hosting infrastructure running cPanel and you haven't verified patch status, stop this podcast and go do that right now.

Alex: Now let's hit the breach cluster, because there was a common thread this week that I think deserves more attention than it got individually. The Trellix source code breach is a supply chain risk story — a security vendor's own code repository gets compromised, and every customer running their product now has to ask whether the exposed code reveals exploitable weaknesses in their deployed defenses. That's a particularly uncomfortable position for security products to be in.

Jordan: Medtronic confirmed a breach from ShinyHunters claiming millions of records. That's the healthcare sector again — it's been a consistent target in 2026 and there's no sign of that abating. But the story that genuinely stopped me was the ransomware negotiators sentenced to four years this week. Two former incident responders — one from Sygnia, one from DigitalMint — were convicted of conducting BlackCat attacks against the companies they were supposed to be protecting. They extorted nearly one-point-three million dollars from a single victim.

Alex: I've been a CISO. I've hired IR firms. I've sat across the table from incident responders in the worst moments of an organization's security history. The trust that relationship requires is profound. These are the people with your keys, your forensics, your playbooks, your contacts. The idea that that access could be weaponized from the inside is not a theoretical risk anymore. It happened, it was prosecuted, and they're going to prison. But that doesn't undo the damage. CISOs need to think rigorously about how they vet IR partners, what access they're granted, and what monitoring exists on that access even for trusted security personnel.

Jordan: And Cordial Spider and Snarky Spider — two new Scattered Spider-adjacent groups identified by CrowdStrike this week — are speedrunning the same playbook: vishing your helpdesk, abusing SSO pages, getting into SaaS environments fast and leaving almost no forensic trace. The attack surface is almost entirely in your SaaS stack. They're not touching endpoints. They don't need to. If your helpdesk can be socially engineered into resetting MFA, and your SaaS environment doesn't have DLP controls that can detect bulk data movement, you are exposed to this pattern right now.

Alex: And the PyTorch Lightning supply chain compromise — malicious versions pushed to PyPI, credential theft, GitHub Actions tampering, SSH persistence — is the reminder that your ML teams are running software with the same supply chain risks as everything else in your environment. Software composition analysis needs to cover your data science pipelines, not just your application code.

Jordan: So what was this week? Stepping back, if I had to characterize it in a single sentence: this was the week where the AI-as-accelerant thesis stopped being theoretical and started showing up in vulnerability disclosures, active exploits, regulatory guidance, and nine-figure acquisition prices simultaneously.

Alex: The Copy Fail vulnerability found by AI. The NCSC warning about AI-accelerated patch waves. Anthropic pulling Mythos because it found thousands of unknown vulnerabilities. AI coding agents with production credentials being targeted by attackers. CISA and the Five Eyes warning about agent identity. Palo Alto and Cisco spending hundreds of millions to address the gap. Every single one of those stories connects back to the same underlying shift: AI is compressing timelines across the entire attack and defense cycle, and the security infrastructure most organizations have was not built for that speed.

Jordan: For CISOs heading into next week, I'd prioritize three things. Patch Linux and cPanel — those are immediate. Audit what credentials your AI tools hold in production — that's the IAM blind spot that's actively being exploited. And if you have any exposure to digital assets or crypto infrastructure, DPRK is not a background threat, it's a foreground one.

Alex: And take the CISA-NSA AI agent guidance seriously. Not because of what it says today, but because of what it signals about where compliance expectations are heading. Get ahead of it now, when you have runway, rather than scrambling when it becomes a requirement.

Jordan: The week in security was fast. Next week will probably be faster.

Alex: That's the Week in Review for the week ending May 2nd, 2026. The daily show returns Monday. If this episode was useful, share it with the peers in your network who need the synthesis. I'm Alex Chen.

Jordan: I'm Jordan Reeves. Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-02.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 6 topic areas, including: DHS Shutdown Ends as CISA Faces Long Recovery; Claude Code, Copilot and Codex all got hacked. Every attacker went for the credential, not the model.; US ransomware negotiators get 4 years in prison over BlackCat attacks.

BankInfoSecurity · May 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: CISA's 75-day shutdown and ongoing workforce losses directly degrade the federal cyber defense ecosystem that enterprises rely on for threat intelligence, vulnerability coordination, and incident response support.

📖 Read full article

VentureBeat Security · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Six research teams demonstrating that AI coding agents hold and expose production credentials without human session anchoring represents a fundamental IAM blind spot that CISOs must address as developer teams adopt these tools.

📖 Read full article

BleepingComputer · May 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Former incident responders at reputable firms using insider knowledge to conduct ransomware attacks highlights the insider threat from trusted security partners and the need for rigorous vetting of third-party IR vendors.

📖 Read full article

CyberScoop · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: New Com-affiliated groups replicating Scattered Spider's voice phishing and fake SSO tactics against SaaS environments represent an immediate threat to enterprises relying on identity-based perimeter defenses and helpdesk-based authentication resets.

📖 Read full article

BankInfoSecurity · May 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The NASCIO-Deloitte survey showing only 22% of state CISOs feel their data is protected signals a broader erosion of public-sector cyber posture that affects enterprise partners, supply chains, and regulated industries dependent on government data exchanges.

📖 Read full article

CyberScoop · Apr 30 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Another 45-day Section 702 extension prolongs uncertainty around surveillance authorities that affect enterprise data handling obligations, particularly for cloud providers and companies managing cross-border data flows.

📖 Read full article

BankInfoSecurity · May 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A Cisco acquisition of Astrix would consolidate non-human identity management into a major platform vendor, potentially reshaping how enterprises manage service accounts, API keys, and machine identities across hybrid environments.

📖 Read full article

CyberScoop · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: cPanel manages millions of web hosting accounts; an auth bypass exploited as a zero-day since February means any enterprise with web properties on shared hosting or cPanel-managed infrastructure needs immediate remediation.

📖 Read full article

Jordan: The people your company hired to stop a ransomware attack were running one. Let that sit for a second.

Alex: It's Friday, May 1st, 2026. Welcome to Cleartext. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we're covering the end of CISA's 75-day shutdown and what the recovery actually looks like, a pattern in AI coding agent exploits that should change how you think about IAM, two new threat groups copying Scattered Spider's playbook almost verbatim, the ransomware-as-insider-threat story Jordan just teased, a critical cPanel auth bypass that's been in the wild since February, and a Cisco acquisition that signals where the non-human identity market is heading. There's a lot on the table, so let's get into it.

Jordan: Start with CISA, because this sets the backdrop for everything else today. The 75-day DHS shutdown is over. Bipartisan bill passed the House, funding restored. And the instinct is to say fine, problem solved. It isn't. CISA spent two and a half months in reactive posture. No proactive threat hunting, degraded coordination with sector risk management agencies, and a workforce that was already depleted before the shutdown started. The people who left during those 75 days are not coming back because a continuing resolution passed.

Alex: And CISOs need to recalibrate what they expect from the federal ecosystem right now. CISA's threat intelligence sharing, its vulnerability coordination, its support during major incidents — those functions are diminished. Not gone, but diminished. If your security program had CISA in the dependency column as a backstop, you need to reweight that assumption. The public-private partnership model still exists, but the partner on the public side just went through a serious operational disruption.

Jordan: The proposed cuts still on the table make this worse. Even with funding restored, CISA is operating with institutional memory gaps and a smaller headcount. That affects KEV list updates, it affects JCDC coordination, it affects how fast sector-wide advisories move. Plan accordingly.

Alex: Speaking of the KEV list, CISA did manage to push out a critical add this week. cPanel's authentication bypass, CVE-2026-41940, is now confirmed actively exploited. What makes this particularly bad is the timeline: active exploitation has been ongoing since at least February. That's roughly two months of zero-day window before a patch existed. If your organization has any web properties sitting on shared hosting infrastructure or cPanel-managed environments, this needs to go to the top of your remediation queue today, not next sprint.

Jordan: The attack surface here is easy to underestimate. cPanel manages millions of hosting accounts globally. It's not just small businesses — enterprises often have marketing sites, regional properties, dev environments running on infrastructure they don't fully inventory. Auth bypass at the hosting control panel layer means an attacker can pivot into anything managed under that account.

Alex: Now let's talk about the story that connects directly to where your developers are spending their time. The VentureBeat piece from yesterday pulled together six months of research findings on AI coding agents — Claude Code, GitHub Copilot, OpenAI Codex — and the pattern is unambiguous. Every exploit went after credentials held by the agent, not the model itself.

Jordan: The BeyondTrust finding is the one that should keep IAM architects up at night. A crafted GitHub branch name — that's the attack vector — was sufficient to steal Codex's OAuth token in cleartext. OpenAI rated it Critical P1. And separately, Adversa found that Claude Code would silently ignore its own deny rules once a command chain exceeded 50 subcommands. The agent's own policy enforcement broke down under load.

Alex: Here's the business framing for this. Your developers are adopting these tools whether you've formally approved them or not. These agents operate with persistent credentials — OAuth tokens, API keys, sometimes service account access — and they're running autonomously in contexts that your IAM team almost certainly hasn't modeled. There's no human session anchoring. Traditional MFA assumptions don't apply. You have machine identities accumulating privileges in your development pipeline and nobody's auditing them.

Jordan: The fix isn't to ban the tools. That battle's already lost. The fix is to apply the same rigor to AI agent identities that you apply to service accounts. Least privilege, rotation schedules, behavioral monitoring. Treat the agent's credential surface the way you'd treat a privileged service account, because that's functionally what it is.

Alex: Which is a nice segue into why Cisco is reportedly in talks to acquire Astrix Security for somewhere between two-fifty and three-fifty million. Astrix is a non-human identity management play — service accounts, API keys, OAuth grants, machine-to-machine access. The market is getting crowded with point solutions and Cisco is trying to consolidate it into their identity stack. For CISOs, the strategic read here is that the major platform vendors have recognized non-human identity as a distinct, unsolved problem. If Cisco closes this deal, expect that to accelerate similar moves from Microsoft, Palo Alto, and CrowdStrike.

Jordan: Now let's get to the insider threat story, because this is a genuinely alarming data point. Two former incident responders — one from Sygnia, one from DigitalMint, both reputable firms — were sentenced this week to four years each for conducting BlackCat ransomware attacks against five companies in 2023. They extorted nearly 1.3 million dollars from one victim alone.

Alex: These were people who understood IR playbooks from the inside. They knew how defenders respond, what forensic artifacts get prioritized, how to time attacks to maximize leverage. The board question this raises is uncomfortable but necessary: how rigorously are you vetting the third parties who have privileged access to your environment during your worst moments? Most IR retainer agreements involve deep forensic access, and most vendor vetting processes don't go deep enough on the individuals who will actually show up when the incident happens.

Jordan: This isn't a reason to stop retaining IR firms. It is a reason to ask harder questions. Background checks on named responders, not just company-level due diligence. Logging and monitoring of IR firm activity in your environment during engagements. Treating your IR vendor's access the way you'd treat any privileged third party. The trust model has to be zero-trust even in a crisis.

Alex: Sticking with the threat actor landscape, CrowdStrike published research this week on two new Com-affiliated groups — Cordial Spider and Snarky Spider — and they are essentially running the Scattered Spider playbook with minor variations. Voice phishing, fake SSO pages, targeting SaaS environments, rapid data exfiltration for extortion. The speed-to-exfil is what's notable. These groups are optimized for getting data out fast, not for dwell time.

Jordan: The Scattered Spider playbook worked spectacularly well against organizations with strong perimeter defenses but weak helpdesk authentication controls. The lesson from that wave should have been: your helpdesk is an attack surface. If a caller can social engineer a password reset or an MFA bypass, your identity perimeter is made of paper. These new groups are betting that lesson hasn't been learned broadly enough. Based on the research, they're right.

Alex: Before we get to the outlook, a quick note on state CISOs. The 2026 NASCIO-Deloitte survey dropped this week and the headline number is stark: only 22% of state CISOs say their data is protected from cyberthreats. That's not a rounding error, that's a collapse in confidence. Shrinking budgets, AI-enabled attacks, and third-party vendor risk are the drivers.

Jordan: The enterprise relevance here is supply chain and regulatory. If your organization exchanges data with state agencies — healthcare, financial services, critical infrastructure, any regulated sector — the security posture on the other end of that exchange just got a lot harder to trust. And Section 702 getting another 45-day extension rather than comprehensive reauthorization means compliance teams planning cross-border data flows are still operating in uncertainty. That's the third consecutive short-term punt on this.

Alex: Alright, the week's emerging theme. Jordan, what's the thread you're pulling on?

Jordan: Institutional erosion across every layer of the defense stack simultaneously. CISA degraded. State CISOs at their lowest confidence in years. Congress unable to make durable decisions on surveillance law. AI tooling creating IAM blind spots faster than policy can catch up. And threat actors — both nation-state and criminal — who are absolutely tracking all of this. The attack surface isn't just technical. It's structural.

Alex: And the board conversation that comes out of this week is about dependencies. Which of your security assumptions rest on external institutions — federal agencies, trusted vendors, established playbooks — that are currently under strain? Because this week gave us evidence that several of those dependencies are shakier than the org chart suggests. That's the risk assessment conversation to have before summer planning cycles close.

Jordan: Validate your assumptions. Especially the ones you haven't questioned in a while.

Alex: That's Cleartext for Friday, May 1st. If this episode was useful, share it with a peer. We'll be back Monday. Have a good weekend.

Jordan: Stay clear.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-05-01.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 6 topic areas, including: Srsly Risky Biz: US Vows to Fight Distillation Attacks; Lotus Wiper Attack Targets Venezuelan Energy Firms, Utilities; Everyone’s building AI agents. Almost nobody’s ready for what they do to identity..

Risky Business News · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The US government's formal response to Chinese AI distillation attacks and the shift of Chinese threat actors to botnet-based operations represent two converging threats — CISOs must account for both AI IP theft risks and the increasing difficulty of detecting nation-state activity hidden within botnet infrastructure.

📖 Read full article

Dark Reading · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Destructive wiper malware targeting critical infrastructure with sophisticated living-off-the-land techniques is a growing pattern globally — CISOs in energy and utilities should review detection capabilities for LotL-based data destruction campaigns.

📖 Read full article

CyberScoop · Apr 30 · Relevance: █████████░ 9/10

Why it matters to CISOs: Anthropic withholding its Mythos model due to its ability to discover thousands of unknown vulnerabilities signals a paradigm shift in threat modeling — CISOs must prepare for a world where AI agents massively expand the attack surface through non-human identity sprawl and autonomous vulnerability discovery.

📖 Read full article

The Hacker News · Apr 29 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Any enterprise running SAP with Node.js integrations needs immediate software composition analysis — this supply chain compromise of SAP-related npm packages could expose credentials across development and production environments.

📖 Read full article

TechCrunch Security · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Two separate cyber incidents resulting in $3M+ losses at a sovereign finance ministry underscore the risk of payment system compromise — a cautionary case for any CISO managing treasury or payment operations, especially in environments with limited security resources.

📖 Read full article

CyberScoop · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Designating data centers as a standalone critical infrastructure sector would trigger new regulatory obligations and could reshape compliance requirements for any enterprise operating or colocating in major data center facilities.

📖 Read full article

Cybersecurity Dive · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The Deloitte-NASCIO study reflecting declining CISO confidence mirrors pressures across the private sector — AI complexity and budget constraints are forcing difficult trade-offs that enterprise CISOs should use as leverage in board-level resource discussions.

📖 Read full article

BankInfoSecurity · Apr 30 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A $250M–$350M Cisco acquisition of Astrix validates non-human identity as a critical enterprise security category and could reshape how organizations manage service accounts, API keys, and machine identities within Cisco-centric environments.

📖 Read full article

BleepingComputer · Apr 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: cPanel/WHM powers millions of web hosting environments including many enterprise-managed web properties — an actively exploited authentication bypass with public PoC demands immediate patching or mitigation, especially for organizations with legacy web infrastructure.

📖 Read full article

Jordan: Anthropic built an AI model that found thousands of vulnerabilities hiding in major operating systems and browsers — some of them sitting undetected for nearly thirty years. Then they decided not to release it. Let that sink in for a moment.

Alex: This is Cleartext. I'm Alex Chen. Thursday, April 30th, 2026. Today we're covering a lot of ground — AI agents breaking identity frameworks, the US government drawing a line on Chinese AI theft, a supply chain attack inside the SAP ecosystem, a destructive wiper hitting Latin American energy infrastructure, and a critical cPanel zero-day that's been exploited in the wild for months. Jordan, let's get into it.

Jordan: Let's start with the Anthropic Mythos story because the implications are significant and I don't think the security community has fully processed them yet. Anthropic built this model, Mythos, watched it discover thousands of previously unknown vulnerabilities across major operating systems and browsers — flaws that had been sitting dormant for up to three decades — and then said, we're not putting this in the world. That's a responsible decision. But the decision itself tells you everything about where we are.

Alex: Right. The responsible disclosure isn't the story. The capability is the story. Because if Anthropic got there, others are getting there. And some of those others are not going to make the same call.

Jordan: Exactly. And the CyberScoop piece frames this correctly — the deeper problem is that AI agents are creating a category of non-human identity that existing IAM frameworks simply weren't designed for. We're not talking about a service account you provision once and forget. We're talking about autonomous agents making decisions, calling APIs, accessing systems, spawning other agents. The identity surface area is expanding in ways that aren't being tracked.

Alex: This is the conversation I've been having with peers for six months. Most organizations can't give you an accurate inventory of their human identities, let alone machine identities. And now we're adding agents that can act autonomously, that can inherit permissions, that can operate across trust boundaries — and nobody's governing that. The Cisco move to acquire Astrix starts to make more sense in this context. If the rumored $250 to $350 million acquisition goes through, it signals that Cisco sees non-human identity as a tier-one security category, not a niche problem. That's validation worth noting when you're going to your board asking for budget to address identity sprawl in your agentic environment.

Jordan: And for listeners who are already deploying AI agents in any capacity — pilots, internal tools, copilots with elevated access — the question you need to be asking right now is: who governs the identity lifecycle of that agent? What credentials does it hold? What can it access? How do you revoke it? If you can't answer those questions, you have a gap.

Alex: Let's pivot to the geopolitical thread because there are two converging stories here. The US government is formally stepping in to address what the intelligence community is calling distillation attacks — Chinese AI labs extracting the capabilities of frontier models by querying them at massive scale. You ask the right questions, in the right sequence, you can reverse-engineer what makes a model powerful without ever touching its weights.

Jordan: It's model theft through the API. And it's elegant, which is why it's a problem. The countermeasures are hard. You can rate-limit, you can detect anomalous query patterns, but at scale, with sophisticated adversaries rotating through different access vectors, this is not a solved problem. The US government stepping in suggests the commercial ecosystem hasn't been able to contain it on its own.

Alex: The second thread is the botnet shift among Chinese threat actors. Broad adoption of botnet infrastructure for operations. Attribution becomes dramatically harder. Detection becomes harder. But the flip side — and the Risky Biz write-up makes this point — is that botnets are also more disruptible. Authorities can seize nodes, take down infrastructure. So there's an enforcement opportunity embedded in the problem.

Jordan: For defenders, though, the immediate practical implication is this: if you're hunting for nation-state activity in your environment using traditional IOC-based attribution, you're going to miss more. Botnet traffic blends. You need behavioral detection, anomaly-based approaches. The signatures aren't going to save you.

Alex: Now let's talk about Lotus Wiper, because this is a pattern that matters regardless of geography. Destructive wiper malware, living-off-the-land techniques, targeting Venezuelan energy firms and utilities. No flashy custom tools. Just the operating system's own capabilities turned against itself.

Jordan: LotL-based wipers are specifically hard to detect because you're looking for legitimate tools doing illegitimate things. The forensic trail is designed to look like normal system activity until it isn't. Energy sector CISOs specifically — your detection logic needs to account for this. If you're not running behavioral baselines that can distinguish admin activity from destructive activity, that's where the gap is.

Alex: And Latin America is not an isolated case. This is a pattern we've seen in Ukraine, in the Middle East, increasingly wherever there's geopolitical instability. The technique migrates. Your sector might not be today's target, but the playbook travels.

Jordan: SAP. Let's go there. Supply chain attack targeting SAP-related npm packages, credential theft, multiple research firms flagging it simultaneously.

Alex: If you run SAP — and a significant portion of our audience does — this needs to be in your incident response queue today. The attack vector is Node.js integrations, npm packages that developers pull in as part of SAP ecosystem development. Compromised packages with credential-stealing malware. The breadth of the research response — Aikido, Onapsis, Wiz, Socket, others — suggests the campaign was widespread enough that multiple teams hit it independently.

Jordan: Run your software composition analysis now. Map your SAP-adjacent development pipelines. If you have developers pulling in packages from the SAP ecosystem via npm, you need to know what versions they're using and whether those versions are clean.

Alex: Brief note on the Sri Lanka situation — two separate cyber incidents, over three million dollars lost, targeting the finance ministry. I raise this not because it's a massive number in absolute terms, but because the pattern matters. Two incidents in rapid succession suggests the initial response didn't close the underlying vulnerability. And the context — a country still recovering from sovereign debt crisis, constrained security resources — that's a cautionary tale for any organization operating lean. Resource constraints don't reduce your threat exposure. They just reduce your ability to respond.

Jordan: cPanel. CVE-2026-41940. Authentication bypass, critical severity, actively exploited since late February, public proof of concept now available.

Alex: If you have cPanel or WHM in your environment — and many enterprises do through managed hosting or legacy web properties — this is a patch-now situation. It was already being exploited before the PoC dropped. With the PoC public, the exploitation bar just got lower. Check your versions. If you're not on the latest release, you're exposed.

Jordan: And worth flagging: the "late February" detail means this was a zero-day for months before public disclosure. That's a reminder that patching at disclosure time still means you were behind.

Alex: Before we close out, let's talk about the broader theme this week, because I think there is one. Congress is debating whether to designate data centers as standalone critical infrastructure. State CISOs are reporting declining confidence in their ability to manage cyber risk — the Deloitte-NASCIO data is striking — and that mirrors what I'm hearing from private sector peers. The combination of AI complexity, budget pressure, and expanding attack surface is creating a confidence gap that's real and that boards need to understand.

Jordan: The non-human identity problem, the AI distillation problem, the agentic vulnerability discovery problem — they're not separate issues. They're all facets of the same transition. We're moving into an environment where the threat actors have AI capability, where the attack surface is being reshaped by AI, and where the defensive frameworks we built for a human-speed, human-scale threat environment are starting to show their age.

Alex: What to watch: the Cisco-Astrix deal, if it closes, will be a signal to the entire identity market. Watch whether other major platform vendors make similar moves in the next 90 days. The non-human identity category is going to consolidate fast. And on the regulatory side, if that data center designation moves forward, the compliance implications are significant for any enterprise with meaningful data center footprint.

Jordan: And watch the AI model governance question. Anthropic made a responsible call on Mythos. Not everyone will.

Alex: That's Cleartext for Thursday, April 30th. If this episode was useful, share it with a peer. We'll be back tomorrow. Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-04-30.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 4 topic areas, including: Risky Bulletin: Ukrainians hacked Russian satellite comms platform; Chinese National Extradited Over Silk Typhoon Cyber Campaign; Germany Caught Up in Likely Russian Signal Phishing.

Risky Business News · Apr 29 · Relevance: █████████░ 9/10

Why it matters to CISOs: A successful Ukrainian offensive cyber operation against Russian satellite communications demonstrates the escalating sophistication of state-level attacks on critical infrastructure, reinforcing the need to assess satellite and comms dependencies in enterprise resilience planning.

📖 Read full article

Infosecurity Magazine · Apr 28 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The extradition of an alleged MSS-directed Silk Typhoon operator signals escalating law enforcement action against Chinese state-sponsored espionage and validates the persistent threat that APT campaigns pose to enterprise intellectual property and sensitive data.

📖 Read full article

BankInfoSecurity · Apr 29 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Russian phishing attacks compromising senior German government officials via Signal highlight that encrypted messaging platforms are not immune to social engineering, and CISOs should ensure executive communications security includes phishing-resistant authentication for messaging apps.

📖 Read full article

The Record (Recorded Future) · Apr 28 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Foreign adversary election targeting campaigns often spill over into corporate environments through disinformation, spear-phishing, and infrastructure hijacking; CISOs should heighten awareness during election cycles.

📖 Read full article

Infosecurity Magazine · Apr 28 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A major medical device manufacturer confirming a breach claimed by ShinyHunters underscores ongoing supply chain and third-party risk in healthcare, and signals board-level scrutiny around health data protection and notification obligations.

📖 Read full article

BleepingComputer · Apr 28 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Continued law enforcement action against Scattered Spider members is relevant to CISOs whose organizations have faced social engineering and SIM-swapping attacks from this group; the arrest demonstrates the threat group is still actively targeted by authorities.

📖 Read full article

Ars Technica Security · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Security vendors themselves becoming targeted in supply chain attacks highlights the recursive trust problem in enterprise security toolchains; CISOs must evaluate vendor security posture as rigorously as their own.

📖 Read full article

BankInfoSecurity · Apr 29 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A potential $250M-$350M Cisco acquisition of Astrix validates non-human identity as a critical security category and could reshape the identity security vendor landscape CISOs rely on for service accounts, API keys, and machine identity management.

📖 Read full article

The Hacker News · Apr 29 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: LiteLLM is widely used as an LLM gateway/proxy in enterprise AI deployments; a critical pre-auth SQLi flaw exploited within 36 hours of disclosure means any organization using LiteLLM in production must patch immediately or risk full database compromise.

📖 Read full article

Jordan: Ukrainian hackers just took down a Russian satellite communications platform. State-level offensive cyber is no longer a spectator sport, and today we're going to talk about what that means for the rest of us.

Alex: Welcome to Cleartext. It's Wednesday, April 29th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Today we've got a dense one. State-sponsored threat actors are having a busy week — Russia, China, the Ukraine conflict going fully cyber. We've got a Medtronic breach confirmed by ShinyHunters, a supply chain attack targeting your security vendors directly, a critical flaw in enterprise AI infrastructure being exploited within 36 hours, and Cisco making a move that could reshape how you think about machine identity. A lot to get through. Let's go.

Alex: Start with Ukraine, because that satellite story is genuinely significant and not just for the obvious reasons.

Jordan: So Ukrainian hackers compromised a Russian satellite communications platform. No small thing. Satellite comms are strategic infrastructure — military coordination, logistics, command and control. This isn't a defacement or a data leak. This is Ukraine demonstrating that it can reach into and disrupt Russian strategic communications infrastructure. From a threat intelligence standpoint, this matters for enterprise security leaders because it marks another milestone in the normalization of offensive cyber as a legitimate wartime tool at scale. We are watching the doctrine being written in real time.

Alex: And the business implication here isn't abstract. If you are any organization with satellite communications dependencies — and more companies have them than realize it, especially in manufacturing, energy, maritime, aviation — you need to be asking your resilience team right now: if a satellite comms provider goes dark, what's our fallback? This is the kind of scenario that used to live only in government continuity planning. It belongs in your enterprise BCP today.

Jordan: The ripple effect is the thing. Sophisticated offensive cyber capabilities developed and refined in conflict zones have a history of migrating. NotPetya started as a Ukrainian operation and took down half the global shipping industry. That's not hypothetical. That's recent history.

Alex: Speaking of state-sponsored campaigns with long tails — the Silk Typhoon extradition. A Chinese national has been extradited to the US for alleged involvement in the MSS-directed Silk Typhoon campaign. This is significant on multiple levels.

Jordan: First, the operational signal: the US government is willing to pursue extradition for MSS-connected hackers, which means the intelligence community has enough confidence in attribution to put it in a courtroom. That's a high bar. Second, the campaign itself — Silk Typhoon was targeting COVID-19 research, pharmaceutical IP, biotech. If your organization plays anywhere near life sciences, this is a reminder that the Chinese intelligence apparatus views your R&D as a legitimate collection target, and has for years.

Alex: The extradition also functions as deterrence signaling, even if the operational impact on MSS activities is minimal in the short term. For CISOs, the board-level framing here is straightforward: nation-state actors are targeting intellectual property with the explicit backing of foreign governments. That is a material risk that belongs in your threat model and your D&O conversations.

Jordan: Staying in the state-sponsored lane — Germany, Signal, and Russian phishing. This one deserves more attention than it's getting.

Alex: Walk us through it.

Jordan: Russian actors ran a phishing campaign against senior German government officials — including the president of the Bundestag — through Signal. Signal came out and said, correctly, that this isn't a platform vulnerability. Signal's encryption held. This was social engineering. Linked devices, QR code abuse, convincing pretexts. The platform didn't fail. The humans did.

Alex: And that is exactly the wrong lesson to take if you walk away thinking "Signal is fine, no problem here." The lesson is that encrypted messaging gives you confidentiality in transit. It does not protect you from an adversary who tricks your executive into linking a malicious device to their account. If you have pushed Signal or any encrypted messaging app to your executive team as your secure comms solution — which many of us have — you need to pair that with training on device linking, session management, and phishing-resistant authentication for the account itself.

Jordan: The Kremlin has been running social engineering operations against European governments for years. This isn't new tradecraft. What's notable is the target profile — parliament-level officials — and the success rate. If it's working at that level, assume it's being attempted against your C-suite.

Alex: Let's move to breaches. Medtronic is a big one. ShinyHunters claimed access. Medtronic confirmed it. Millions of records allegedly accessed from one of the largest medical device companies in the world.

Jordan: ShinyHunters has a track record. They don't usually bluff. And Medtronic confirming the breach removes any ambiguity. The healthcare sector continues to be a target-rich environment — regulated data, complex supply chains, legacy infrastructure, and notification obligations that create significant legal and reputational exposure the moment something goes wrong.

Alex: For CISOs in healthcare and for anyone with healthcare clients or partners, the immediate concern is HIPAA notification timelines, but the strategic concern is third-party and supply chain exposure. Medtronic's ecosystem includes hospitals, device integrators, software platforms. If you're downstream of a breach like this, you need to understand your contractual obligations and your own exposure. Don't wait for Medtronic's notification letter to start that analysis.

Jordan: Scattered Spider — a 19-year-old dual US-Estonian citizen arrested in Finland, now facing federal charges in the US. This group brought down MGM and Caesars. This kid was allegedly a prolific member.

Alex: The arrest matters less for what it does to Scattered Spider's operational capacity — these groups are resilient — and more for what it confirms: law enforcement is actively pursuing members across jurisdictions. Finland, the US, coordinated. The group is not operating with impunity. But the social engineering playbook they developed is now widely copied. Assume the TTPs outlast the arrests.

Jordan: Now the supply chain story that should make every CISO uncomfortable. A recent attack specifically targeted Checkmarx and Bitwarden. Two security vendors. One does code security scanning with privileged access to your source code repositories. The other manages your passwords.

Alex: This is the recursive trust problem stated plainly: when your security vendors get compromised, attackers get the keys to everything those vendors touch. And these aren't generic vendors — Checkmarx sits inside your SDLC pipeline with access to proprietary code, and Bitwarden manages credential vaults. If you are a customer of either, you need to be reviewing what access those platforms have to your environment and what your incident response plan looks like if a tier-one security vendor is breached.

Jordan: Vendor security assessments need to be treated with the same rigor as your own internal security reviews. This story is a data point in an argument we've been making for years. The perimeter is your vendor ecosystem now.

Alex: Quick but important — Cisco is reportedly in talks to acquire Astrix Security, a non-human identity startup, for somewhere between 250 and 350 million dollars. That's a 25% premium on a 200 million dollar valuation.

Jordan: Non-human identity is the category. Service accounts, API keys, OAuth tokens, machine-to-machine credentials. Most organizations have an order of magnitude more non-human identities than human ones and a fraction of the governance around them. The market is validating this. Cisco buying into it tells you where the puck is going.

Alex: If you haven't done a non-human identity audit, this is your signal. The acqui-hire market moves before the breach headlines do. Budget conversations around NHI governance just got easier to have.

Jordan: And fast — LiteLLM. CVE-2026-42208. CVSS 9.3. Pre-authentication SQL injection. Exploitation started within 36 hours of disclosure. LiteLLM is a widely used open-source LLM gateway in enterprise AI deployments.

Alex: If you have LiteLLM in production, patch it today. Not this week. Today. Pre-auth means no credentials required to exploit. Full database compromise is the exposure. This is the kind of vulnerability that makes a great breach disclosure paragraph six months from now if you don't act immediately.

Jordan: The 36-hour exploitation window is also a data point for your vulnerability management program broadly. Mean time to patch needs to be measured in hours for critical pre-auth remote vulnerabilities, not the two-week patch cycles most organizations still run.

Alex: So what's the theme this week, Jordan?

Jordan: State actors are operating with more sophistication, more coordination, and more ambition than ever — satellite infrastructure, encrypted messaging platforms, parliament-level targets. And at the same time, the criminal ecosystem is keeping pace. ShinyHunters, Scattered Spider — these groups have nation-state-level operational discipline without the diplomatic constraints.

Alex: What I'd watch: the election threat warning from Gen. Rudd at Cyber Command is the thing that could define the next six months. He told Congress midterms are in the crosshairs. Foreign adversary election campaigns generate spear-phishing infrastructure, disinformation operations, and domain spoofing that bleeds into corporate environments. Heighten your executive awareness programs now, before the noise ramps up.

Jordan: And watch the Cisco-Astrix deal. If that closes, expect consolidation in the NHI space to accelerate. Your current vendor landscape for machine identity could look very different by Q4.

Alex: That's Cleartext for Wednesday, April 29th. If this was useful, share it with a peer who needs the signal without the noise. We're back tomorrow.

Jordan: Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-04-29.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 6 topic areas, including: Risky Bulletin: New fingerprinting technique can track Tor users; Researchers Identify Fast16 Sabotage Malware That Pre-Dates Stuxnet; Mythos Changed the Math on Vulnerability Discovery. Most Teams Aren't Ready for the Remediation Side.

Risky Business News · Apr 27 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: This roundup covers multiple geopolitically significant items: a new Tor de-anonymization technique, Intellexa's US exploit supply chain ties, US accusations of Chinese AI theft, and expanded US router bans — all of which inform threat modeling and supply chain risk for enterprise security leaders.

📖 Read full article

Infosecurity Magazine · Apr 27 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: The discovery of ICS sabotage malware predating Stuxnet underscores how long nation-state actors have targeted industrial control systems — relevant context for CISOs defending OT environments and assessing long-dwell-time threats.

📖 Read full article

The Hacker News · Apr 27 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Anthropic's Claude Mythos Preview is fundamentally changing the volume and speed of vulnerability discovery, creating an asymmetric remediation burden that CISOs must plan for — teams need to rethink prioritization workflows, SLAs, and staffing models now.

📖 Read full article

Infosecurity Magazine · Apr 27 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: With 75% of cybersecurity staff pessimistic on pay and half actively job hunting, CISOs face acute retention risk — this data is critical for workforce planning conversations with HR and the board.

📖 Read full article

TechCrunch Security · Apr 27 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Itron serves hundreds of millions of homes and businesses with water/energy monitoring infrastructure — a breach here has potential cascading effects on critical infrastructure supply chains and raises questions about OT/IT segmentation for any utility CISO or CISO with critical infrastructure dependencies.

📖 Read full article

BankInfoSecurity · Apr 27 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: HHS OCR continues to enforce heavily on inadequate risk analysis — the single most common HIPAA violation. CISOs in healthcare and adjacent industries should use this as ammunition to secure investment in formal risk assessment programs and documentation.

📖 Read full article

BankInfoSecurity · Apr 27 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Non-human identity management is a fast-growing blind spot for enterprises; a $250M-$350M Cisco acquisition of Astrix would signal market validation and likely reshape how NHI is bundled into enterprise security stacks, affecting procurement and architecture decisions.

📖 Read full article

The Hacker News · Apr 27 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Software supply chain attacks via developer tooling represent a serious enterprise risk — 73 malicious VS Code extensions targeting developers could compromise source code and CI/CD pipelines, and CISOs should ensure extension governance policies are in place.

📖 Read full article

Jordan: A critical infrastructure company serving hundreds of millions of homes just filed an 8-K disclosing it was hacked. That's not a threat model exercise. That's Monday morning.

Alex: Welcome to Cleartext. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: It's Monday, April 27th, 2026, and we have a dense one today. The Itron breach, the AI vulnerability discovery gap that's about to break most security teams, new research rewriting the history of nation-state OT attacks, a Cisco acquisition that tells you where identity security is headed, HIPAA fines that should be on your CFO's desk, and a developer supply chain campaign that flew under the radar for too long. Let's get into it.

Jordan: So Itron. For anyone who doesn't immediately recognize the name — this is the company behind the smart meters and monitoring infrastructure in water and energy utilities across hundreds of millions of homes and businesses. They disclosed unauthorized third-party access to internal systems via an SEC 8-K filing over the weekend. No confirmed operational disruption yet, but the filing itself tells you the legal team assessed this as material.

Alex: And that's the first thing I'd flag for anyone listening. The 8-K trigger. Itron made a judgment call that this clears the materiality bar under the SEC's incident disclosure rules. That's not a technicality — that's a signal. If you're a CISO at a utility, at a municipality, or at any organization with Itron in your supply chain, your question this week is: what data, what credentials, what network access did Itron hold that touches your environment?

Jordan: The IT/OT segmentation question is real here. Itron sits at the seam between enterprise IT and operational infrastructure. A breach of their internal systems doesn't automatically mean meter networks are compromised, but the attack surface for lateral movement into customer environments is worth mapping right now. Don't wait for Itron's investigation to conclude.

Alex: Agreed. Vendor notification letters are coming — eventually. Don't let that be your trigger to start the assessment.

Jordan: Let's move to the research that rewrites history a little. Security researchers have identified a piece of malware called Fast16 that appears to predate Stuxnet and may have been used to target Iran's nuclear program. If that's confirmed, it pushes the start date of nation-state ICS sabotage operations back meaningfully — we're talking about a timeline that predates what most people treat as the origin point of this category of threat.

Alex: The strategic implication here isn't historical curiosity. It's that nation-state actors have been developing and deploying ICS-targeted capabilities for longer than most OT security programs have even existed. If you're defending industrial infrastructure and your threat model starts at Stuxnet, you're already behind the curve on dwell time assumptions, detection gaps, and the sophistication of what's already potentially in your environment.

Jordan: Exactly. Fast16 is a reminder that these programs have institutional memory. They iterate. They go dormant. And the teams defending critical infrastructure need to assume adversary capabilities that are significantly older and more patient than the incident reports suggest.

Alex: Now let's talk about something that I think is the most strategically significant story of the week, even though it reads like a product news item. Anthropic's Claude Mythos Preview has been live for about three weeks, and the security community has been wrestling with what it actually means in practice. The headline from The Hacker News today is blunt: Mythos changed the math on vulnerability discovery, and most teams aren't ready for the remediation side.

Jordan: This is the asymmetry problem. AI-driven discovery at scale means the front end of the vulnerability management pipeline just got dramatically more productive. That sounds good until you realize your remediation capacity — the developers, the patch processes, the SLAs, the prioritization workflows — hasn't changed. You've widened the intake valve without touching the drain.

Alex: I've been thinking about this as a debt acceleration problem. Most organizations are already carrying remediation backlogs they can't close. Mythos-class tooling doesn't solve that — it accelerates the accumulation. And when your board asks you about vulnerability exposure, you're going to have a much harder time explaining why you have ten times the findings and the same closure rate.

Jordan: The teams that get ahead of this are the ones having the resource conversation now. Not after they've run the tool, generated three thousand findings, and watched their SLA compliance crater. The question to take to your CISO peers: what does your prioritization model look like when discovery volume doubles or triples? If the answer is "we'll triage harder," that's not an answer.

Alex: Related to that talent conversation — Harvey Nash dropped a workforce survey today that every CISO should print out and bring to their next HR meeting. Seventy-five percent of cybersecurity staff are pessimistic about pay. Half are actively job hunting. Half.

Jordan: And that's not a surprise if you've been paying attention, but the timing is brutal. You've got AI tools creating more work, not less. You've got an expanding attack surface. And you're trying to retain the people who actually know where the bodies are buried in your environment — which is irreplaceable institutional knowledge — while competing against companies that are paying significantly above market.

Alex: This is a board conversation. Not an HR conversation. If half your security team is interviewing elsewhere, that is an operational risk that belongs in your risk register. Frame it that way.

Jordan: A few items worth moving through at speed. First: HHS OCR just handed out $1.7 million in HIPAA fines across four organizations — a medical imaging provider, a women's healthcare group, a health plan, and a third-party insurance administrator. The violation in every case: inadequate or nonexistent security risk analysis.

Alex: OCR has been beating this drum for years. Risk analysis failures are the single most cited HIPAA violation, and regulators keep finding the same gap after every ransomware investigation. If you're in healthcare or adjacent to it, this is your documentation audit moment. The fine isn't the real cost — it's that OCR found ransomware AND no defensible risk analysis. That combination is what escalates from fine to consent decree.

Jordan: On the supply chain front — researchers uncovered 73 fake VS Code extensions on the Open VSX repository tied to an infostealing campaign called GlassWorm. Six confirmed malicious, the rest acting as sleepers or decoys. These are cloned versions of legitimate extensions. Developers install them thinking they're getting the real thing.

Alex: Developer tooling as an attack vector is not new, but the scale here matters. VS Code is everywhere. If you don't have an extension governance policy — an approved list, enforcement at the IDE level, monitoring for unapproved installs — this is a gap that could put source code and CI/CD credentials at risk. Your dev teams are a high-value target. Treat their environments accordingly.

Jordan: Now for the acquisition story. Cisco is reportedly in talks to acquire Astrix Security — a non-human identity startup — for somewhere between two-fifty and three-fifty million. That's a meaningful premium on their last valuation.

Alex: Non-human identities — service accounts, API keys, OAuth tokens, machine credentials — are the identity management problem most organizations have barely started solving. The ratio of non-human to human identities in a typical enterprise is now somewhere between ten-to-one and fifty-to-one depending on how cloud-native you are. If Cisco closes this deal, it signals that NHI is graduating from niche product category to core platform feature. Watch how this affects your Cisco negotiations and your identity architecture roadmap.

Jordan: And briefly on the Risky Business roundup from today — two items worth flagging. First, there's a new fingerprinting technique that can de-anonymize Tor users. For most enterprise CISOs this is background noise, but for anyone with threat intelligence operations or staff using anonymization infrastructure for sensitive research, that anonymity assumption just got weaker. Second, the US router ban has been expanded to include WiFi hotspots. That's supply chain hygiene at the network edge — worth a review of what's deployed in remote offices and field locations.

Alex: So what's the theme coming out of today? I think it's capacity. Every major story this week is a capacity problem in disguise. Itron is about the capacity of critical infrastructure vendors to secure their own environments. Mythos is about the capacity of security teams to remediate what AI discovers. The workforce data is about the capacity of organizations to retain the people doing the work. The HIPAA fines are about the capacity — or failure — to document risk analysis properly.

Jordan: The adversaries are scaling. The tools are scaling. The regulatory expectations are scaling. The question every CISO should be asking this week is: what's my actual throughput? Not what's my posture on paper — what can my team actually process, validate, and close in a given sprint?

Alex: If the answer makes you uncomfortable, that discomfort belongs in front of your board. That's the conversation that unlocks budget.

Jordan: Watch the Itron investigation this week. If scope expands into customer environments, this gets significantly more complex for utility CISOs.

Alex: That's Cleartext for Monday, April 27th. If this was useful, share it with a peer who needs the brief. We're back tomorrow. Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-04-27.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 18 stories across 6 topic areas, including: A dozen allied agencies say China is building covert hacker networks out of everyday routers; AI Tools Are Helping Mediocre North Korean Hackers Steal Millions; Iran’s cyber threat may be less ‘shock and awe’ than ‘low and slow,’ officials say.

CyberScoop · Apr 23 · Relevance: █████████░ 9/10

Why it matters to CISOs: This multi-nation advisory signals a fundamental shift in Chinese APT tradecraft toward industrialized botnets from compromised edge devices—CISOs need to map and baseline traffic from all edge devices, especially routers and VPN concentrators.

📖 Read full article

Wired Security · Apr 22 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: AI is democratizing offensive capabilities for nation-state hackers—even less-skilled DPRK operators stole $12M in three months using AI for everything from malware coding to fake websites, lowering the bar for sophisticated attacks.

📖 Read full article

The Record (Recorded Future) · Apr 24 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Reframing Iran's cyber threat as opportunistic and persistent rather than dramatic changes defensive priorities—CISOs in critical infrastructure should focus on detecting stealthy, long-dwell intrusions rather than preparing solely for destructive attacks.

📖 Read full article

Ars Technica Security · Apr 21 · Relevance: █████████░ 9/10

Why it matters to CISOs: Mythos finding 271 bugs in a mature codebase signals AI-driven vulnerability discovery is now operationally real—CISOs must consider both the defensive acceleration this enables and the offensive implications if adversaries gain similar capabilities.

📖 Read full article

Infosecurity Magazine · Apr 21 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Two-thirds of firms reporting AI agent-related incidents validates the urgency for CISOs to establish governance frameworks for autonomous AI agents before they become the next major attack surface.

📖 Read full article

Ars Technica Security · Apr 23 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Ransomware adopting post-quantum cryptography signals that recovery via future cryptanalytic breakthroughs is off the table—CISOs must double down on prevention, backup integrity, and resilience rather than hoping for future decryption capabilities.

📖 Read full article

CyberScoop · Apr 23 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The Vercel breach—originating from a single employee's OAuth grant to a third-party AI tool—illustrates why CISOs must govern OAuth token grants and third-party AI tool integrations as first-class attack surfaces.

📖 Read full article

Krebs on Security · Apr 21 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The Scattered Spider guilty plea reinforces that social engineering and SMS phishing remain the most effective initial access vectors—CISOs should ensure help desk and employee authentication procedures are hardened against these techniques.

📖 Read full article

Infosecurity Magazine · Apr 22 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: This insider threat case is a wake-up call for CISOs using third-party ransomware negotiation services—vetting, separation of duties, and oversight of IR vendors must be rigorous to prevent conflicts of interest.

📖 Read full article

Infosecurity Magazine · Apr 24 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Half a million health research records appearing on Chinese e-commerce platforms underscores the geopolitical dimension of health data theft—CISOs in healthcare and research organizations must treat biomedical data as a national security asset.

📖 Read full article

BleepingComputer · Apr 23 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A security vendor's own analysis tool being compromised via Docker images and VS Code extensions is a trust-shattering event—CISOs must verify integrity of security tooling itself and implement supply chain controls even for trusted vendors.

📖 Read full article

BleepingComputer · Apr 24 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: ADT's breach by ShinyHunters highlights the ongoing risk from extortion groups targeting consumer-facing companies with large customer datasets—CISOs in similar verticals should review data minimization practices and extortion response playbooks.

📖 Read full article

CyberScoop · Apr 22 · Relevance: ████████░░ 8/10

Why it matters to CISOs: CISA's leadership vacuum deepens at a time of escalating threats—CISOs relying on federal coordination and guidance should plan for continued uncertainty in federal cyber leadership and policy direction.

📖 Read full article

CyberScoop · Apr 22 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A federal privacy law would reshape data governance obligations across the enterprise—CISOs should evaluate how their current privacy programs align with Virginia/Kentucky-style frameworks this bill is modeled on.

📖 Read full article

CyberScoop · Apr 24 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Section 702 reauthorization directly affects how intelligence agencies can compel enterprise cooperation on surveillance—CISOs at cloud and telecom providers should track this for potential new compliance obligations.

📖 Read full article

BankInfoSecurity · Apr 25 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Cisco's potential $250-350M acquisition of Astrix validates non-human identity as a critical security category—CISOs should evaluate their own NHI posture given that machine identities now vastly outnumber human ones.

📖 Read full article

BankInfoSecurity · Apr 25 · Relevance: █████████░ 9/10

Why it matters to CISOs: The Firestarter backdoor surviving reboots, upgrades, and standard remediation on Cisco firewalls means CISOs must reassess their edge device integrity verification processes and potentially plan for hardware-level inspections.

📖 Read full article

VentureBeat Security · Apr 21 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Prompt injection in AI coding agents affecting Claude, Gemini, and Copilot demonstrates that AI-assisted development workflows are now a concrete attack vector—CISOs must enforce strict controls on AI agent permissions in CI/CD pipelines.

📖 Read full article

Jordan: Every once in a while you get a week where the threat landscape doesn't just evolve — it accelerates. This was that week. Chinese APT groups industrializing botnets out of your edge devices. A confirmed backdoor on Cisco firewalls that laughs at your remediation playbook. AI finding two hundred and seventy-one zero-days in Firefox in what I can only assume was an afternoon. If you took a few days off this week, welcome back — you have some reading to do.

Alex: You're listening to Cleartext. I'm Alex Chen, with me as always is Jordan Reeves, and this is our Saturday Week in Review. If the daily episodes piled up in your queue, no judgment — here's what actually mattered this week and what it means for your program going into Monday. We've got four big themes to work through. Nation-state tradecraft took a significant step forward, and we have the joint advisories to prove it. The AI threat surface expanded in three distinct and uncomfortable directions simultaneously. The breach ledger had some entries that should shape how you think about third-party risk and your own IR vendors. And on the governance side, the leadership vacuum at CISA got worse. Let's get into it.

Jordan: So the geopolitical story of the week — and I'd argue the story of the quarter — is that twelve allied agencies put out a joint advisory on Chinese APT groups building covert networks out of compromised routers and edge devices. Twelve nations. That's not a routine threat bulletin, that's a coordinated diplomatic signal dressed up as technical guidance. What they're describing is a fundamental shift in Chinese offensive tradecraft. These groups have moved away from targeted, bespoke intrusion infrastructure toward industrialized botnets built from the devices sitting at the edge of your network right now. Your SOHO routers, your VPN concentrators, your firewalls. The tradecraft advantage here is real — when your malicious traffic originates from a legitimate IP in someone's home or small business network, attribution becomes genuinely hard, and detection requires a baseline you probably don't have.

Alex: And I want CISOs to hear that last part clearly. Do you have a baseline for what normal looks like on your edge devices? Not your endpoints — your routers, your concentrators, your network edge. For most organizations the honest answer is no, and that's precisely the gap these groups are exploiting. The advisory does include actionable detection guidance, which is relatively unusual for a document like this. Your team should pull that and work through it this week.

Jordan: The second China-adjacent story that connects here is the UK Biobank breach. Half a million health research records — genomic data, health histories — appeared for sale on Chinese e-commerce platforms. A UK government minister confirmed it. And I think CISOs in healthcare and research need to sit with that for a second. This isn't just a GDPR problem. Biomedical data at scale is a national security asset. The adversary understands that even if your legal team is still framing it as a privacy compliance issue.

Alex: Alongside the China picture, we got some important context on Iran this week that I actually found useful as a framing correction. US officials are pushing back on the idea that Iran's cyber posture is primarily about shock-and-awe attacks. The assessment is more nuanced — Iran is operating low and slow, opportunistic intrusions that are designed to look bigger than they are. There's separate reporting about AI-generated malware targeting Israeli water infrastructure, assessed as ineffective, but the direction of travel matters. The implication for CISOs, particularly in energy, water, and critical infrastructure — you're not primarily preparing for a dramatic destructive event. You're hunting for stealthy, long-dwell intrusions that have been in your environment for months.

Jordan: Now let's talk about the AI theme, because it ran through almost every story this week in different ways. And I want to separate three distinct vectors here because they're easy to conflate. First is AI as an offensive force multiplier for adversaries. The Wired reporting on North Korean hackers this week was genuinely clarifying. We've spent a lot of energy worrying about nation-state actors with elite technical capabilities. The DPRK story flips that — one group of operators that analysts describe as mediocre stole up to twelve million dollars in three months using AI for malware development, fake company websites, social engineering scripts, the works. AI is not just making good hackers better. It's making average hackers dangerous. That changes your threat model.

Alex: The second AI vector is AI as a vulnerability discovery engine, and this one is frankly the most consequential for the long term. Anthropic's Mythos model found two hundred and seventy-one security vulnerabilities in Firefox 150. Mozilla's own CTO said the model is every bit as capable as the world's best security researchers. Let me put that in board-level language. The window between vulnerability existence and exploitation just collapsed. If a well-resourced adversary has access to similar capability — and we should assume they either do or will soon — the notion that you have thirty days to patch a disclosed vulnerability becomes a fiction. Your patching cadence, your compensating controls, your detection posture — all of it needs to be rethought against a world where vulnerability discovery is automated and fast.

Jordan: The third AI vector this week was internal — AI agents as a new attack surface inside the enterprise. Two stories converged on this. Cloud Security Alliance data showed two thirds of firms have already experienced cybersecurity incidents related to AI agents — data exposure, operational disruption, financial loss. At the same time, researchers at Johns Hopkins demonstrated prompt injection attacks through GitHub PR titles that caused Claude, Gemini CLI, and GitHub Copilot to leak their own API keys. The attack required no external infrastructure. Just a malicious pull request title. If your developers are running AI coding agents in CI/CD pipelines — and eighty-five percent of enterprises are piloting this — you have an active attack surface that most security teams are not governing.

Alex: And I want to add the Checkmarx story here because it connects. Hackers compromised Docker images and VS Code extensions for Checkmarx's own KICS security analysis tool. A security vendor's tooling became the attack vector. When you add that to the AI agent prompt injection research, you're looking at a developer environment where the tools themselves cannot be fully trusted. That's a supply chain problem with implications for how you govern your software development lifecycle end to end.

Jordan: On breaches — and there were several worth your attention — the Vercel incident is the one I'd spend the most time on. The origin point was a single employee's OAuth grant to a third-party AI tool called Context AI. The breach expanded to additional customer accounts during the investigation, Mandiant got called in, and the downstream exposure is still being scoped. This is the story you use when your board asks why you care about OAuth token hygiene. One OAuth grant to one AI productivity tool opened a breach that is affecting Vercel's customers and their customers. Map your OAuth grants. Govern third-party AI tool integrations like the attack surface they are.

Alex: Two guilty pleas this week that are worth flagging. First, a member of Scattered Spider — Tyler Buchanan, twenty-four years old — pleaded guilty to wire fraud and aggravated identity theft. His group hacked twelve major tech companies using SMS phishing. There is nothing technically sophisticated about what Scattered Spider does. It is social engineering, it is help desk manipulation, it is exploiting the gap between your security policies and how your people actually behave under pressure. If you haven't hardened your help desk authentication procedures and employee identity verification recently, this is your reminder. The second plea was more disturbing. A ransomware negotiator named Angelo Martino admitted he was secretly working for BlackCat while nominally representing victims in negotiations. He was helping maximize ransom amounts against the organizations that hired him. I don't want to overstate the frequency risk here, but the implication is clear — your IR vendor relationships need oversight, vetting, and separation of duties. Trust but verify applies to the people you call when things go wrong.

Jordan: There's also the Firestarter backdoor story that broke Friday and I want to make sure it doesn't get lost in the weekend news cycle. CISA issued an emergency directive over a backdoor on Cisco Firepower and ASA devices that survives reboots, upgrades, and standard remediation. A joint US-UK advisory. The backdoor was discovered on a federal civilian agency network that had been compromised since September 2025. Seven months. If you have Cisco edge devices — and most of you do — your current remediation playbook is insufficient for this threat. You need to pull the CISA guidance and think about what hardware-level integrity verification actually looks like in your environment.

Alex: Quickly on the governance front — CISA's nominated director Sean Plankey withdrew his nomination this week after waiting more than a year for Senate confirmation. I don't want to editorialize too much on the politics but the operational implication is real. CISA is the federal coordination layer for threat intelligence sharing, emergency directives, and incident response support. It has been operating in chaos. If any part of your security program leans on federal guidance or coordination — and it probably should — you need contingency posture for the possibility that coordination remains degraded for the foreseeable future. Build more peer relationships. Lean harder on ISACs. Don't assume the federal backstop is reliable right now.

Jordan: On the privacy legislation front — House Republicans released a federal privacy bill modeled on Virginia and Kentucky state frameworks. No bipartisan support, uncertain path to passage. Our take — don't restructure your data governance around this bill. But do use the moment to benchmark your current program against where federal legislation is likely to land eventually. The direction is set even if the timing isn't.

Alex: And the market note — Cisco reportedly in talks to acquire non-human identity startup Astrix Security for somewhere between two-fifty and three-fifty million. For CISOs this is a category validation signal. Machine identities now vastly outnumber human ones in most enterprise environments and most programs are not governing them with anything like the rigor applied to human identity. If you don't have a clear answer to the question of what non-human identities exist in your environment and what access they have, that's a gap that deserves priority this quarter.

Jordan: So what was this week? If I had to name it — this was the week the attack surface became simultaneously wider and faster. Wider because edge devices, AI agents, developer tooling, OAuth grants, and IR vendors all showed up as active attack vectors in real incidents. Faster because AI-driven vulnerability discovery and AI-enabled adversaries are compressing the timelines we've historically built our programs around.

Alex: The through-line I'd bring to your board is this. For the better part of a decade the security conversation was about complexity — too many tools, too much data, too much noise. This week was a preview of a different problem. Adequate defenses are getting harder to define because the offense is accelerating faster than most programs can track. That's not a counsel of despair — it's an argument for ruthless prioritization. Edge device integrity. AI agent governance. OAuth hygiene. Help desk authentication. Those are your four action items going into the week.

Jordan: Get those Cisco advisories in front of your team Monday morning. Don't let the weekend bury them.

Alex: That's the week. Thank you for spending part of your Saturday with us. Cleartext returns Monday with daily coverage. If this episode was useful, share it with a peer who needed the catch-up. We'll see you next week.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-04-25.

Sources are pulled from: CyberScoop, The Record, SecurityWeek, Krebs on Security, Dark Reading, Cybersecurity Dive, BleepingComputer, Wired, Ars Technica, TechCrunch, Help Net Security, VentureBeat, Risky Business News, The Hacker News, CISA, and BankInfoSecurity.