Cleartext

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 6 topic areas, including: A dozen allied agencies say China is building covert hacker networks out of everyday routers; Surveillance campaigns use commercial surveillance tools to exploit long-known telecom vulnerabilities; In a first, a ransomware family is confirmed to be quantum-safe.

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

Why it matters to CISOs: A joint advisory from 12+ allied agencies describing China's tactical shift to botnet-based covert networks demands immediate review of edge device hygiene, network visibility, and threat hunting for SOHO router compromises across your environment.

📖 Read full article

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

Why it matters to CISOs: First-ever mapping of attack traffic to mobile signaling infrastructure exposes how commercial surveillance vendors exploit SS7/Diameter weaknesses—CISOs with mobile-dependent executives or operations in sensitive regions face direct espionage risk.

📖 Read full article

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

Why it matters to CISOs: Ransomware operators adopting post-quantum cryptography before most enterprises do is a stark wake-up call—this eliminates any future hope of decrypting seized ransomware payloads and reinforces the urgency of resilient backup and recovery strategies.

📖 Read full article

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

Why it matters to CISOs: Vercel's expanding breach scope—now confirmed to affect additional customers and downstream third-party systems—is a concrete supply-chain risk for any enterprise running applications on Vercel infrastructure, requiring immediate assessment of exposure.

📖 Read full article

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

Why it matters to CISOs: A compromise of security tooling itself—Checkmarx KICS Docker images and IDE extensions—represents a nightmare scenario where the tools CISOs rely on for code analysis become attack vectors, demanding immediate verification of developer tool integrity.

📖 Read full article

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

Why it matters to CISOs: CISA leadership vacuum continues to deepen—Plankey's withdrawal after a year of chaotic interim leadership raises serious questions about federal cyber coordination, incident response partnership, and the reliability of government threat intelligence sharing for the private sector.

📖 Read full article

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

Why it matters to CISOs: A $72M Series C for artifact-level supply chain security signals strong market validation for the category—CISOs evaluating software composition and artifact trust solutions should track Cloudsmith's expanding capabilities in policy enforcement and real-time package risk.

📖 Read full article

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

Why it matters to CISOs: Cisco's potential $250-350M acquisition of Astrix Security validates non-human identity as a critical enterprise gap—CISOs should consider how service accounts, API keys, and machine identities are governed ahead of likely platform consolidation.

📖 Read full article

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

Why it matters to CISOs: FIRESTARTER malware persisting on Cisco ASA/Firepower devices even after patching means CISOs must go beyond patch management—integrity verification and forensic examination of perimeter firewalls is now urgent, especially given CISA confirmed a federal agency was compromised.

📖 Read full article

Jordan: Patching your Cisco firewall isn't enough anymore. CISA confirmed a federal agency had a backdoor sitting on their perimeter device for months — and it survived the patch. Let that sink in for a second before your morning coffee kicks in.

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

Jordan: And I'm Jordan Reeves.

Alex: Big week. We're covering a 12-agency warning about China industrializing router botnets, FIRESTARTER malware that laughs at your patch management program, the Vercel and Checkmarx breaches expanding in ways that should concern every CISO with a modern software supply chain, quantum-safe ransomware — yes, really — SS7 surveillance campaigns finally mapped to real infrastructure, CISA's leadership vacuum getting worse, and two market signals worth tracking. Let's get into it.

Jordan: Let's start with what I'd call the week's most strategically significant story, and it's a two-header. First: CISA, NCSC-UK, and ten other allied agencies dropped a joint advisory on China-linked groups systematically compromising consumer and SOHO routers to build covert proxy networks. We're talking about industrialized botnet infrastructure built out of the kind of hardware sitting in your employees' home offices, your branch locations, and your OT-adjacent networks. The tactical logic here is sound from their perspective — commodity hardware, hard to attribute, blends into legitimate traffic.

Alex: And the board-level read on this is straightforward. If your visibility stops at the enterprise perimeter, you're blind to traffic routing through these networks. The advisory has specific defensive recommendations, and I'd encourage your team to treat this as a hunting trigger, not a reading exercise. Edge device hygiene, firmware integrity, network telemetry on anomalous egress patterns. The sophistication here isn't in the malware — it's in the operational concept. They're using your ISP's forgotten hardware against you.

Jordan: Layer that on top of the second geopolitical story this week, and you start to see a coherent espionage doctrine. Researchers published what they're calling the first-ever mapping of commercial surveillance tool traffic to mobile operator signaling infrastructure. SS7 and Diameter vulnerabilities aren't new — we've known about them for a decade. What's new is seeing the commercial surveillance industry actually fingerprinted in real attack traffic, with vendors posing as legitimate carriers to track physical locations.

Alex: If you have executives traveling in sensitive regions, or mobile-dependent operations anywhere with contested geopolitical exposure, this is not an abstract problem. The attack surface is the phone your CFO carries to Singapore. The mitigations are limited — encrypted messaging apps help for comms, but location tracking via SS7 doesn't care about your Signal installation. This is a risk conversation you need to have with your board, particularly around executive protection programs.

Jordan: Now to the story I opened with — FIRESTARTER. CISA and NCSC confirmed a backdoor on a US federal agency's Cisco ASA and Firepower devices. Active since at least September 2025. In March 2026, attackers returned to already-patched devices without re-exploiting the original vulnerability. The persistence mechanism survived standard remediation. That is not a patching failure. That is a fundamental assumptions failure.

Alex: This is the story where I want CISOs to stop and have a hard conversation with their teams. For years we've operated on the assumption that patch equals remediation. FIRESTARTER breaks that. The attacker got in, established persistence at a layer below what your standard patch touches, and waited. Your next step is not patching — it's integrity verification of your perimeter devices. Firmware hashes, configuration baselines, and frankly forensic review if you have Cisco ASA or Firepower in your environment and you haven't done a clean rebuild recently. The CISA advisory has IoCs. Use them this week.

Jordan: And speaking of assumptions that need revisiting — let's talk supply chain, because this week handed us two concrete examples of why the category keeps expanding. Vercel disclosed that the scope of their April breach is larger than initially reported. More customers affected, downstream third-party systems compromised, and — critically — the full scope of exposure is still undefined. Undefined scope is the phrase that should make your general counsel uncomfortable.

Alex: If you're running applications on Vercel infrastructure, you need an answer to two questions today. What data flows through that environment, and what downstream systems are connected to it? Supply chain breaches are particularly brutal because the blast radius is discovered in stages. Every new disclosure from Vercel is another opportunity for your organization to find itself in scope. Get ahead of it.

Jordan: The Checkmarx KICS story is arguably more insidious, because this time it's the security tooling itself. Attackers compromised Docker images and VSCode and Open VSX extensions for the KICS infrastructure-as-code analysis tool — and used those artifacts to harvest credentials and sensitive data from developer environments. Your AppSec tool became the attack vector.

Alex: This one hits differently because KICS is specifically a security product. The trust assumption was baked in. The action item here is verifying the integrity of your developer and security tooling supply chain — not just your application dependencies, but the tools your developers use every day. Hash verification, provenance checks, pull from verified sources only. And yes, that Cloudsmith Series C we'll mention in a moment is directly relevant to this problem.

Jordan: Quantum-safe ransomware. I'll give you a moment with that phrase. Researchers confirmed the first ransomware family using post-quantum cryptography. There is no practical operational benefit to this for the attacker today. Quantum computers capable of breaking current encryption don't exist at scale. So why are they doing it?

Alex: A few possibilities. It's a marketing move within ransomware-as-a-service ecosystems — differentiation for sophisticated buyers. It's future-proofing against a capability they believe is coming sooner than we do. Or it's signaling that criminal operators are tracking NIST's PQC standards as closely as your compliance team. What it means for CISOs is this: the leverage in ransomware recovery — the occasional government seizure that yields decryption keys — that leverage just got harder to apply. Resilient, tested, offline backups. That's the mitigation. It's unglamorous and it works.

Jordan: CISA governance. Sean Plankey withdrew his nomination to lead the agency. This follows over a year of interim leadership, budget turbulence, and staff departures. I'm going to be direct: CISA's effectiveness as a threat intelligence partner to the private sector is degraded right now. That doesn't mean you ignore their advisories — this week's Cisco and China router alerts are proof they're still producing valuable work. But your strategic dependence on federal coordination as a backstop for your program needs to be recalibrated. Don't plan around CISA as an active operational partner in an incident response scenario the way you might have three years ago.

Alex: Two market signals worth thirty seconds each. Cloudsmith closed a $72 million Series C for artifact-level software supply chain security — policy enforcement, auditability, real-time package risk. Given what we just said about Checkmarx KICS, the timing is almost illustrative. If you're evaluating the category, it's worth a look. And Cisco is reportedly in talks to acquire Astrix Security for $250 to $350 million. Astrix focuses on non-human identity — service accounts, API keys, machine identities. This is a category that's been underserved relative to its actual risk surface, and Cisco putting that kind of number on it is validation that platform vendors see it as table stakes. If you haven't done an audit of your non-human identity sprawl, this deal is your signal to start.

Jordan: Stepping back to the week's theme — and there is a clear one. The perimeter is lying to you. Patched Cisco firewalls are hiding backdoors. Security tooling is delivering malware. Proxy networks are routing through your employees' home routers. The adversary has methodically attacked every assumption layer we've built defenses on.

Alex: What strikes me is how much of this week's news is about persistence and concealment over speed and destruction. Whether it's FIRESTARTER waiting eight months on a firewall, or China's router botnet blending into legitimate ISP traffic, or SS7 surveillance mapped invisibly to carrier infrastructure — the strategic posture is patience. They're not blowing doors open. They're learning to live inside.

Jordan: Which means detection has to be the investment priority. Not more prevention layers. Better visibility, better hunting, better forensic capability on the things you already own. The signals are there. The question is whether you have the instrumentation and the people to see them.

Alex: That's the right note to end the week on. For CISOs, the action items are concrete: forensic review of Cisco perimeter devices, supply chain integrity verification of developer tooling, risk conversation with your board on executive mobile exposure, and a clear-eyed reassessment of your federal coordination dependencies.

Jordan: All the links are in the show notes. Have a good weekend — or at least a quiet one.

Alex: This is Cleartext. See you Monday.

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

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: China’s cyber capabilities now equal to the US, warns Dutch intelligence; Hackers deployed wiper malware in destructive attacks on Venezuela’s energy sector; Ransomware, fraud, and lawsuits drive cyber insurance claims to new peaks.

The Record (Recorded Future) · Apr 22 · Relevance: █████████░ 9/10

Why it matters to CISOs: A Western intelligence agency formally assessing China as a peer-level cyber adversary reframes risk models for any enterprise with exposure to Chinese supply chains, IP, or operations in the Asia-Pacific region.

📖 Read full article

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

Why it matters to CISOs: Wiper attacks on energy infrastructure signal continued escalation of destructive cyber operations against critical sectors—CISOs in energy, utilities, and adjacent industries should review resilience and recovery playbooks.

📖 Read full article

Help Net Security · Apr 23 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Hard data on ransomware severity ($508K average), remote access as the dominant entry vector (87% of ransomware claims), and rising claim frequency gives CISOs concrete evidence for board-level risk quantification and insurance renewal planning.

📖 Read full article

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

Why it matters to CISOs: A breach of a national identity document agency represents a high-severity identity fraud risk for any enterprise with French employees or customers, and raises questions about government-held PII security across jurisdictions.

📖 Read full article

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

Why it matters to CISOs: A self-propagating worm that steals npm tokens and spreads through compromised repositories represents a novel escalation in software supply chain attacks that could affect any enterprise running JavaScript/Node.js applications.

📖 Read full article

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

Why it matters to CISOs: CISA's continued leadership vacuum directly affects federal cybersecurity guidance, threat advisories, and public-private coordination that enterprise security teams depend on for incident response and threat intelligence.

📖 Read full article

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

Why it matters to CISOs: A federal privacy law would reshape data handling obligations, potentially preempting the patchwork of state laws that CISOs currently navigate, but lack of bipartisan support signals this may stall—worth tracking for compliance planning.

📖 Read full article

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

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

📖 Read full article

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

Why it matters to CISOs: An actively exploited zero-day in Microsoft Defender—a ubiquitous enterprise endpoint tool—with CISA issuing emergency patching orders means this requires immediate attention across virtually all Windows environments.

📖 Read full article

Jordan: Dutch intelligence just told the world something that most Western security leaders weren't ready to hear out loud: China is now a peer-level cyber adversary to the United States. Not close. Not approaching. Peer. Let that sit for a moment before we get into everything else today.

Alex: Welcome to Cleartext. It's Thursday, April 23rd, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we're covering the Dutch intelligence assessment on China's cyber capabilities, a wiper attack on Venezuela's energy sector, fresh data from the cyber insurance market that your CFO is going to want to see, France's national ID agency breach, a self-propagating supply chain worm in the npm ecosystem, the ongoing CISA leadership vacuum, a federal privacy bill that may or may not matter, a notable acquisition in the non-human identity space, and an actively exploited zero-day in Microsoft Defender. Tight show today. Let's get into it.

Jordan: The lead story is the Dutch AIVD assessment, and it matters for reasons beyond the headline. Western intelligence agencies don't use the word "peer" casually. For years, the framing around China was "sophisticated but below US capability." That framing is now officially retired, at least in The Hague. What the Dutch are actually saying is that Chinese cyber operations are so technically refined that they are routinely evading both intelligence agencies and commercial defenders. Routinely. That's not a warning about potential. That's a damage assessment.

Alex: And here's the board implication that CISOs need to sit with. If your current risk model treats China as a capable but detectable threat, you have a model problem. The defensive gap that the Dutch are describing—where operations are being missed at the intelligence community level—means that enterprise telemetry alone is not going to catch this. If you have IP that's competitively valuable, manufacturing in the Asia-Pacific region, or supply chain exposure to Chinese vendors, you need to be having a very different conversation about assumed compromise versus detection-first postures.

Jordan: The geopolitical context here also matters. This assessment isn't coming from Washington. It's coming from a close NATO ally with its own robust intelligence apparatus and, frankly, significant economic exposure to China. When the Dutch say this publicly, they're accepting diplomatic friction to make the point. That tells you how serious they believe the situation is. This isn't political positioning. This is a professional intelligence judgment.

Alex: Let's connect the second geopolitical story here because it's thematically related, even if the geography is different. A previously unknown wiper malware was deployed against Venezuela's energy and utilities sector. No ransom demand, no data exfiltration objective. The goal was destruction.

Jordan: Wiper campaigns are the clearest signal that an attacker's objective is not financial—it's coercive or punitive. Venezuela's energy sector has been a geopolitical flashpoint for years. Attribution here is unclear, but the target profile and the tool design both point toward state-level or state-sponsored actors. For CISOs in energy, utilities, and critical infrastructure, the takeaway is not "watch Venezuela." It's that destructive attacks on OT-adjacent environments are an active and escalating pattern globally. Your resilience and recovery posture needs to be tested, not assumed.

Alex: Now let's talk money, because the cyber insurance data out today from At-Bay is exactly what you need to walk into a board meeting or a budget conversation. Overall claim frequency up seven percent year over year. Average severity at an all-time high of two hundred twenty-one thousand dollars. But ransomware is where it gets serious: average claim severity of five hundred eight thousand dollars, up sixteen percent from last year.

Jordan: And the entry vector number is the one that should sting. Eighty-seven percent of ransomware claims in 2025 traced back to remote access services. VPNs, RDP, remote management tools. We have been saying this for years. The insurers now have a hundred thousand policy years of data that confirm it. If you're walking into an insurance renewal and you haven't made demonstrable improvements to remote access security—MFA enforcement, privileged access management, exposed service reduction—you are going to face it at the table.

Alex: Use this report. The five-hundred-eight-thousand-dollar average ransomware severity figure is a concrete number you can put in front of a CFO or a board risk committee to justify controls investment. That's the value of hard actuarial data in a domain that's spent too long arguing from hypotheticals.

Jordan: On the breach front, France confirmed that the government agency responsible for issuing national IDs and passports was compromised. Number of affected citizens: unspecified, which in government-breach language usually means large. The practical concern for enterprise security leaders is twofold. First, if you have French employees or customers, their government-issued identity documents may be compromised, which has real implications for identity verification and fraud risk. Second, this is a reminder that government-held PII repositories are high-value, high-consequence targets, and the controls protecting them are not always commensurate with that value.

Alex: Staying on breach, the CanisterSprawl story is the one your AppSec and DevOps teams need to see today. A self-propagating worm is moving through the npm ecosystem by stealing developer tokens and using those tokens to compromise downstream repositories automatically. It's not just malicious packages sitting in a registry waiting to be pulled. It's a worm that spreads from developer to developer through their own credentials.

Jordan: The exfiltration mechanism is also worth noting. Stolen data is being routed through ICP canisters—decentralized infrastructure that's significantly harder to take down than a conventional C2 server. Whoever built this thought carefully about persistence and resilience. If your engineering teams have npm packages they maintain or contribute to, token hygiene and secrets scanning in your CI/CD pipeline need to be verified, not assumed.

Alex: Two governance stories that belong together. CISA's nominated director, Sean Plankey, has withdrawn after waiting more than a year for Senate confirmation. And House Republicans have dropped a federal privacy bill with no bipartisan support. The CISA story is the more urgent of the two.

Jordan: CISA without permanent leadership during a period of escalating nation-state activity is a structural problem that affects every enterprise security team that depends on federal threat advisories, coordinated vulnerability disclosure, and public-private incident response coordination. The agency is operationally functioning, but strategic direction matters. Watch for impact on the quality and cadence of joint advisories over the coming months.

Alex: On the privacy bill—model it but don't bet on it. A federal standard preempting state law would simplify compliance architectures that are currently managing CCPA, Virginia's CDPA, and an expanding list of state frameworks simultaneously. But without bipartisan support, this stalls. Track it. Don't build a compliance program around it yet.

Jordan: Quick note on the Cisco and Astrix story. Cisco is reportedly in late-stage talks to acquire the non-human identity startup for somewhere between two-fifty and three-fifty million. That's a meaningful premium over Astrix's last valuation and a strong signal that non-human identity—service accounts, API keys, OAuth tokens, machine-to-machine credentials—is now a board-level security category, not a niche product feature. If you haven't audited your non-human identity surface recently, the market is telling you that your adversaries have.

Alex: And before we get to the outlook, the operational item you need to action today: BlueHammer. CISA has added a Microsoft Defender privilege escalation vulnerability to its Known Exploited Vulnerabilities catalog and ordered federal agencies to patch immediately. This is being actively exploited as a zero-day. Microsoft Defender is deployed across the overwhelming majority of enterprise Windows environments. Patch it. Today. No further analysis required.

Jordan: Stepping back to the week's emerging theme: we are watching a maturation of the threat landscape that is outpacing defensive evolution. The Dutch assessment says China is operating at a level that evades professional defenders. The insurance data says remote access—a solved problem technically—is still responsible for nearly nine in ten ransomware entries. CanisterSprawl says supply chain attacks are gaining self-replication capability. These are not incremental changes. The gap between what sophisticated attackers can do and what most enterprise programs are resourced to stop is widening.

Alex: And the governance infrastructure that's supposed to help close that gap—CISA, federal coordination mechanisms, even something as basic as a consistent national privacy framework—is in a moment of significant uncertainty. For CISOs, the implication is that you cannot assume external scaffolding will fill the gaps. The board conversation has to shift from "are we compliant" to "are we resilient when the scaffolding isn't there."

Jordan: Which is, frankly, where it should have been all along.

Alex: That's Cleartext for Thursday, April 23rd. If this was useful, share it with a peer who needs the signal without the noise. We'll be back tomorrow. Stay sharp.

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

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 5 topic areas, including: UK cyber agency handling four major incidents a week as nation-state attacks surge; Pentagon Cyber Leaders Back $1.5T Budget Request; Mozilla: Anthropic's Mythos found 271 security vulnerabilities in Firefox 150.

The Record (Recorded Future) · Apr 22 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The NCSC's disclosure that the UK faces four nationally significant incidents weekly—predominantly from nation-states rather than criminals—signals a material shift in the threat landscape that should inform board-level risk discussions and resilience planning.

📖 Read full article

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

Why it matters to CISOs: The DoD positioning cyber as a core warfighting domain with expanded offensive operations signals increased government activity in cyberspace—CISOs should anticipate both tighter defense-sector compliance requirements and a more contested threat environment as adversaries respond.

📖 Read full article

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

Why it matters to CISOs: An AI model finding 271 vulnerabilities in a major browser signals that both defenders and attackers now have access to autonomous vulnerability discovery at scale—CISOs must factor AI-accelerated exploit timelines into their patching and risk models.

📖 Read full article

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

Why it matters to CISOs: Prompt injection attacks causing Claude Code, Gemini CLI, and Copilot Agent to leak API keys via GitHub PRs demonstrate that AI coding agents are a live attack surface—CISOs must establish guardrails around AI agent integrations in CI/CD pipelines.

📖 Read full article

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

Why it matters to CISOs: This supply-chain breach via an unreviewed third-party AI tool OAuth grant illustrates a growing blind spot: shadow AI integrations creating unmonitored paths into production environments. CISOs need to audit OAuth grants and third-party AI tool access immediately.

📖 Read full article

Cybersecurity Dive · Apr 21 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A suspected North Korea-linked supply chain attack on the widely used axios JavaScript library demands immediate action from security teams to audit dependencies and check for indicators of compromise across development and production environments.

📖 Read full article

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

Why it matters to CISOs: Terrorism designations for ransomware groups targeting hospitals would fundamentally alter the legal landscape—triggering new sanctions, insurance implications, and potentially making ransom payments a federal crime. Healthcare CISOs and their legal teams need to track this closely.

📖 Read full article

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

Why it matters to CISOs: This insider threat case—where a ransomware negotiator colluded with BlackCat to maximize ransoms totaling $75.3M—is a direct warning to CISOs about vetting and segregating duties within incident response vendors and internal IR processes.

📖 Read full article

BankInfoSecurity · Apr 22 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Airbus acquiring a cybersecurity firm specifically to counter AI-driven reverse engineering of aerospace systems signals growing concern about AI-powered attacks on embedded and edge systems—relevant for CISOs in defense, manufacturing, and critical infrastructure.

📖 Read full article

Jordan: An AI model just found 271 zero-day vulnerabilities in Firefox. In one pass. That same class of model is available to every nation-state, every ransomware crew, and every threat actor with a cloud account. If that doesn't reframe your patching strategy conversation with the board, I don't know what will.

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

Jordan: And I'm Jordan Reeves.

Alex: Today we're covering a lot of ground—and most of it points in the same direction. Nation-state tempo is up. AI is reshaping both the offense and the defense. And the software supply chain is having a genuinely bad week. We've got the UK's NCSC sounding alarms at a volume we haven't heard before, two significant supply chain compromises demanding your team's attention right now, a Vercel breach that every CISO with SaaS sprawl should read carefully, and some legislative movement on ransomware that could change the legal calculus overnight. Let's get into it.

Jordan: Start with the UK, because the numbers are striking. The NCSC disclosed this week that they're handling four nationally significant cyber incidents every week. Not incidents broadly—nationally significant ones. And the majority are now attributed to hostile foreign governments, not criminal actors. Their framing is explicit: converging geopolitical tensions plus accelerating technology equals a perfect storm. That's not bureaucratic hedging. That's a warning.

Alex: And the relevance for CISOs outside the UK isn't abstract. What the NCSC is seeing in terms of nation-state tempo and targeting patterns reflects a global shift. When a G7 intelligence agency says the majority of major incidents are state-sponsored, that should land differently in your board risk presentation than the generic "threat landscape is evolving" language we've been using for years. If your board still thinks of nation-states as someone else's problem, these numbers should end that conversation.

Jordan: Reinforcing that, the Pentagon this week told Congress that the new 1.5 trillion dollar budget request positions cyber as a core warfighting domain. The funding covers expanded offensive operations, AI-driven capabilities, and a significant Cyber Command overhaul. The specific framing from defense officials was that adversaries have shifted from espionage to pre-positioned disruptive attacks. That's a meaningful distinction. Espionage steals data. Pre-positioning means they're already inside systems they intend to disrupt at a time of their choosing.

Alex: Two implications for CISOs. First, if you operate in or adjacent to the defense industrial base, compliance requirements are going to tighten, and probably faster than the acquisition cycle can accommodate. Start that conversation with your legal and regulatory teams now. Second, more broadly—when the US is expanding offensive cyber operations and adversaries are responding in kind, the volume and sophistication of activity across the entire internet goes up. The contested environment doesn't stay contained to government networks.

Jordan: Now let's talk about AI and vulnerability discovery, because this is the story I'd be thinking about if I were sitting in a CISO chair today. Anthropic's Mythos model found 271 security vulnerabilities in Firefox 150. Mozilla's own CTO described the model as, quote, every bit as capable as the world's best security researchers. That's not marketing copy—that's the vendor whose product was analyzed saying the AI matched their best humans.

Alex: Here's the strategic problem. This capability isn't proprietary to Anthropic or to defenders. The same class of model, and in some cases the same models, are accessible to well-resourced threat actors. What this does to your patch window assumptions is severe. We've operated on a mental model where there's some lag between a vulnerability existing and an exploit appearing in the wild. That lag is shrinking toward zero for any organization that isn't patching aggressively. This is a conversation to have with your board framed around mean time to patch, not around whether AI is interesting.

Jordan: And the AI risk this week wasn't limited to vulnerability discovery. Researchers at Johns Hopkins demonstrated what they're calling Comment and Control—a prompt injection attack where a malicious instruction embedded in a GitHub pull request title caused Claude Code, Gemini CLI, and GitHub Copilot Agent to each post their own API keys as PR comments. No external infrastructure required. Three separate AI coding agents from three separate vendors, all vulnerable to the same technique.

Alex: This is a live attack surface. If your development teams are using AI agents in CI/CD pipelines—and most of them are at this point—you need to treat those integrations as privileged processes with the same scrutiny you'd apply to any other automated system with production access. The specific vector here involves the pull_request_target trigger, which exposes secrets to fork PRs. That's an immediate configuration audit item. But the broader takeaway is that AI agents are not just productivity tools. They're new attack surface, and most security teams are not yet governing them as such.

Jordan: Staying on supply chain, two significant incidents this week. The Vercel breach is instructive because it's a perfect illustration of how shadow AI creates exposure. One Vercel employee adopted a third-party AI tool. That tool's vendor got hit with an infostealer. The attacker walked through an OAuth grant that nobody had reviewed into Vercel's production environment. Mandiant is engaged, law enforcement notified. The good news is that no npm packages were compromised—that was verified jointly with GitHub, Microsoft, and Socket.

Alex: But the mechanism here is the story. OAuth grants from employee-adopted AI tools are the new shadow IT. Most security teams have reasonable visibility into sanctioned SaaS. They have almost no visibility into the OAuth grants their employees are generating by connecting AI tools to their work accounts. An audit of OAuth grants in your environment—specifically third-party AI tool integrations with access to production systems—is not optional at this point. This is where the breach surface is growing fastest.

Jordan: The second supply chain hit is more urgent in terms of immediate action. CISA issued guidance this week following a compromise of the axios JavaScript library, which has hundreds of millions of weekly downloads. Attribution points to a North Korea-linked actor. CISA's direction is straightforward: review your environments now for indicators of compromise. If axios is in your dependency tree—and the odds are high that it is—this goes to your security team today.

Alex: Now, a story with significant long-term implications, particularly for anyone in healthcare or with healthcare clients. The House Homeland Security Committee held a hearing this week that included serious discussion of terrorism designations for ransomware groups that target hospitals, and homicide charges for attacks that result in patient deaths. A former FBI official endorsed the terrorism classification. This isn't fringe positioning—it's gaining real traction.

Jordan: The legal consequences if this moves forward are substantial. Terrorism designations trigger sanctions frameworks. Ransom payments to designated groups become federal crimes. Insurance coverage under existing cyber policies could become void if paying is legally prohibited. Healthcare CISOs and their general counsel need to be tracking this actively and starting scenario planning now, not when legislation passes.

Alex: And one more governance story worth flagging quickly. A former ransomware negotiator at DigitalMint pleaded guilty this week to colluding with BlackCat to maximize ransoms totaling 75 million dollars across five victim companies. He was the person hired to negotiate on the victim's behalf. The takeaway for CISOs is direct: the IR vendor ecosystem is not uniformly trustworthy. When you're vetting incident response and negotiation partners, you need the same due diligence rigor you'd apply to any third party with privileged access—references, conflict-of-interest disclosures, segregation of duties between negotiation and payment facilitation.

Jordan: One brief item before we close. Airbus is acquiring Quarkslab, a French cybersecurity firm focused on protecting aerospace and defense systems from AI-driven reverse engineering. It's a 100-person shop, but the acquisition rationale matters. Airbus is specifically worried about AI being used to reverse engineer embedded and edge systems in aircraft. For CISOs in defense, manufacturing, and critical infrastructure—this signals where the threat is heading on the OT and embedded systems side.

Alex: So what's the through-line this week? Jordan, I keep coming back to the same thing. The AI acceleration on both sides of this conflict is compressing every timeline we've built our security programs around.

Jordan: That's exactly right. Four major incidents a week in the UK. An AI model matching elite human researchers on vulnerability discovery. Prompt injection taking down three AI coding agents simultaneously. These aren't isolated data points. The threat environment is operating at a tempo that was theoretical two years ago and is operational now. The question for CISOs is whether your risk model has updated to reflect that, or whether you're still presenting to the board using last cycle's assumptions.

Alex: The practical near-term actions from today: audit your OAuth grants with focus on AI tool integrations, check your axios dependency exposure against CISA's guidance, review your CI/CD pipeline permissions for AI agent access, and update your patch window assumptions in light of what autonomous vulnerability discovery means for exploit timelines. And if you're in healthcare, get your legal team reading the terrorism designation language now.

Jordan: All of today's source links are in the show notes.

Alex: Thanks for listening to Cleartext. We're back tomorrow.

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

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: KelpDAO suffers $290 million heist tied to Lazarus hackers; ZionSiphon Malware Targets Water Infrastructure Systems; Adversaries hijacked AI security tools at 90+ organizations. The next wave has write access to the firewall.

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

Why it matters to CISOs: The largest crypto heist of 2026 attributed to North Korea's Lazarus group underscores the persistent nation-state threat to financial infrastructure and the need for enhanced controls around DeFi and cryptocurrency custody operations.

📖 Read full article

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

Why it matters to CISOs: Dedicated OT malware targeting water systems with sabotage capabilities represents an escalation in critical infrastructure threats that CISOs overseeing utilities or ICS environments must factor into their threat models.

📖 Read full article

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

Why it matters to CISOs: Autonomous SOC agents with write access to firewalls, IAM, and endpoints represent an existential governance gap—CISOs deploying agentic security tools must implement privilege boundaries and abuse monitoring before adversaries exploit these capabilities.

📖 Read full article

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

Why it matters to CISOs: This breach illustrates the cascading risk of third-party AI tool integrations with overly privileged OAuth tokens—a pattern CISOs must audit across their SaaS ecosystems immediately.

📖 Read full article

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

Why it matters to CISOs: An insider from a cybersecurity IR firm conducting ransomware attacks is a worst-case insider threat scenario—CISOs should reassess vetting processes and access controls for third-party incident responders.

📖 Read full article

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

Why it matters to CISOs: New Coast Guard cybersecurity rules imposing OT security standards on ports and commercial vessels signal expanding regulatory scope that CISOs in logistics, shipping, and critical infrastructure must prepare for.

📖 Read full article

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

Why it matters to CISOs: FTC expanding enforcement into AI-generated deepfakes and voice cloning scams signals new compliance obligations for organizations deploying or being targeted by AI-generated content.

📖 Read full article

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

Why it matters to CISOs: Three Cisco Catalyst SD-WAN Manager vulnerabilities now confirmed as actively exploited makes this an emergency patching priority for any enterprise running SD-WAN infrastructure.

📖 Read full article

Jordan: Ninety organizations had their AI security tools hijacked. Every one of those tools could only read data. The next generation shipping right now can rewrite your firewall rules. Think about that for a second.

Alex: Welcome to Cleartext. I'm Alex Chen. It's Tuesday, April 21st, 2026. Today we're covering the largest crypto heist of the year and what it means for your financial infrastructure exposure, a new class of OT malware targeting water systems, the autonomous SOC agent governance problem that nobody has solved yet, a breach that started with Roblox cheats on a personal device and ended inside a major cloud platform, and an insider threat scenario straight out of a CISO's worst nightmares. Plus Cisco SD-WAN patching that should already be in your queue. Let's get into it.

Jordan: Let's start with Lazarus, because $290 million doesn't happen in a vacuum. KelpDAO, a DeFi project, lost that amount over the weekend. CISA-level attribution to North Korea's Lazarus group. This is now the largest crypto heist of 2026, and we're only four months in. For context, Lazarus has been systematically dismantling crypto platforms for years to fund Pyongyang's weapons programs. This isn't opportunistic crime. This is state-directed financial warfare with a very specific spending category at the end of it.

Alex: And the board implication here is real even if your organization has nothing to do with DeFi directly. If you hold crypto on the balance sheet, if you custody digital assets for clients, if you have any counterparty exposure to platforms in this ecosystem, you need to model Lazarus as a live threat to your financial operations, not just a headline risk. The sophistication of these operations has grown substantially. We're not talking about phishing a junior employee. These are coordinated multi-vector attacks against smart contract logic, key management, and bridge infrastructure.

Jordan: The thing that concerns me most is that Lazarus has demonstrated a willingness to adapt faster than the defensive community can publish mitigations. They identify the class of vulnerability, they burn it across multiple targets before detection improves, then they pivot. DeFi custody controls need to be treated with the same rigor as SWIFT access controls. Full stop.

Alex: Let's stay in the critical infrastructure lane for a moment because ZionSiphon deserves serious attention. New malware, purpose-built for OT water infrastructure. It has both sabotage capabilities and ICS scanning built in. That combination is significant because it suggests reconnaissance followed by deliberate physical impact as the operational design. This isn't ransomware looking for a payout. This is designed to break things.

Jordan: The ICS scanning component is what tells you about intent. An attacker building a tool with that capability is doing target development inside the network. They want to understand the process control environment before they pull the trigger on sabotage. Attribution is still developing, but the capability profile is consistent with nation-state investment. If you're a CISO at a utility, a water authority, or any industrial operator, this goes straight into your threat model update for Q2.

Alex: Now to the story Jordan opened with, because this one has genuinely large implications for how we're deploying AI in security operations. The VentureBeat reporting documents adversaries using prompt injection against legitimate AI security tools at more than ninety organizations in 2025. Credentials stolen, cryptocurrency taken. Every compromised tool in that wave was read-only. The generation of autonomous SOC agents shipping today is not.

Jordan: We're talking about agents that can rewrite firewall rules, modify IAM policies, quarantine endpoints. And here's the governance nightmare embedded in that: when a compromised agent takes an action, it looks like an authorized API call. Your EDR doesn't flag it. Your SIEM sees expected behavior. The attacker isn't logging in, they're just steering a trusted process that already has the keys.

Alex: This is the conversation I'd be having with my board right now if I were still in the seat. Because the pitch for these tools is compelling. Faster response, twenty-four seven autonomy, analyst capacity expansion. All real benefits. But you cannot deploy write-access autonomy into your security infrastructure without privilege boundaries, scope constraints, and abuse monitoring that are just as rigorous as what you'd apply to a privileged human account. The accountability question also matters. When an agent rewrites a firewall rule based on a poisoned prompt and that causes an outage or a breach, who owns that?

Jordan: My take: any vendor shipping autonomous SOC agents with write access who cannot show you a coherent answer to that question doesn't ship yet. Treat agentic security tools as privileged accounts, audit their actions, and stage write access behind human approval gates until you have confidence in the abuse detection layer.

Alex: Shifting to the Vercel breach, and this is a case study in supply chain risk that every CISO should walk their team through. The attack chain here is almost elegant in how mundane it starts. An employee's personal device. Lumma Stealer malware disguised as Roblox cheat software. That malware harvested OAuth tokens for Context.ai, a third-party AI tool integrated into Vercel's environment. Those tokens had far more privilege than they needed, and lateral movement into Vercel's internal systems followed.

Jordan: The personal device element is important. You don't control what your employees do on personal hardware. But you can control what OAuth tokens issued to third-party integrations are permitted to access and do. This is fundamentally a least-privilege failure at the integration layer.

Alex: This is the audit I'd be running today. Go look at every third-party SaaS integration in your environment. Pull the OAuth scopes. Ask whether each one genuinely requires the access it was granted. My bet is you'll find tokens with read and write access to production systems that were approved during a fifteen-minute vendor onboarding conversation two years ago and never reviewed since.

Jordan: On to Angelo Martino. Former ransomware negotiator at DigitalMint, pleaded guilty to running BlackCat attacks against U.S. companies while working in incident response. He used insider knowledge of victim behavior, negotiation dynamics, and organizational vulnerabilities from his professional role to conduct attacks. If you have a more damaging insider threat scenario in the IR space, I haven't heard it.

Alex: The vetting implication is real. When you bring in a third-party IR firm, you are granting them significant access to your most sensitive systems during your most vulnerable moment. Background checks, reference validation, and access scoping for external responders need to be part of your IR retainer agreement, not an afterthought during the breach. This case is going to be referenced in IR vendor due diligence conversations for years.

Jordan: Quick hits before we get to the outlook. Cisco SD-WAN: CISA has now flagged three separate Catalyst SD-WAN Manager vulnerabilities as actively exploited. CVE-2026-20133 is the latest. Federal agencies got a four-day deadline. You should treat it identically. If you're running SD-WAN infrastructure and you haven't patched these, this is your interruption. Do it today.

Alex: Two regulatory signals worth flagging. The Coast Guard's new OT security rules for ports and commercial vessels are live, and they represent exactly the kind of sector-specific regulatory expansion we've been watching spread from financial services into critical infrastructure verticals. If you have maritime or logistics exposure, get your compliance team reading the rule. And the FTC is expanding its AI enforcement portfolio into deepfakes and voice clone scams. That's not primarily a technical security problem, it's a fraud and brand integrity problem, but it lands on the CISO's desk in organizations where those functions aren't clearly separated.

Jordan: The week's theme, if you're looking for one, is this: trust is being systematically weaponized. Trusted tools, trusted partners, trusted agents. Lazarus trusted as a financial actor, an IR negotiator trusted as a defender, AI tools trusted as security infrastructure, OAuth tokens trusted as authorized access. The attack surface isn't just technical anymore. It's every relationship and delegation in your environment.

Alex: The question for CISOs this week is: what have you trusted that you haven't audited in the last twelve months? Where have you extended privilege, whether to a human, a tool, or a vendor, without a periodic review mechanism? That list is your risk register in a different format.

Jordan: And on the AI agent question specifically: we're at an inflection point. The governance frameworks don't exist yet. The vendors are moving fast. If you're deploying autonomous agents with write access into security operations before you have that framework in place, you are running an experiment with your production environment as the test case.

Alex: That's Cleartext for Tuesday, April 21st. We'll be back tomorrow. If today's episode was useful, share it with someone in your leadership chain who needs to hear the AI agent conversation. Stay sharp.

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

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: Researchers Detect ZionSiphon Malware Targeting Israeli Water, Desalination OT Systems; Finance Chiefs Warn New AI Models May Rattle Global Banking; EU pushes for stronger cloud sovereignty, awards €180 million to four providers.

The Hacker News · Apr 20 · Relevance: █████████░ 9/10

Why it matters to CISOs: A purpose-built OT malware targeting critical water infrastructure signals escalating nation-state cyber-physical threats; CISOs with OT environments must reassess ICS/SCADA segmentation and monitoring.

📖 Read full article

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

Why it matters to CISOs: Global finance officials signaling that AI-accelerated cyber risk is outpacing regulatory frameworks gives CISOs ammunition for board-level conversations about proactive AI governance investments.

📖 Read full article

Help Net Security · Apr 20 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: EU cloud sovereignty investments directly impact multinational CISOs who must plan for data residency requirements and potential mandate shifts toward European-only cloud providers for EU operations.

📖 Read full article

Help Net Security · Apr 20 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A turnkey AI vishing platform available for $4,000 dramatically lowers the barrier for sophisticated social engineering attacks, requiring CISOs to urgently bolster voice-channel awareness training and authentication procedures.

📖 Read full article

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

Why it matters to CISOs: This breach via a compromised third-party AI tool highlights the expanding supply chain attack surface from AI tooling adoption; CISOs must inventory and risk-assess employee-used AI services.

📖 Read full article

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

Why it matters to CISOs: The guilty plea of a Scattered Spider leader underscores law enforcement progress against social engineering-driven cybercrime groups that have targeted major enterprises including MGM and Caesars.

📖 Read full article

BankInfoSecurity · Apr 20 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Survey data showing only 1-in-5 enterprise AI initiatives meeting KPIs due to data security gaps gives CISOs concrete evidence to advocate for stronger data governance before scaling AI further.

📖 Read full article

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

Why it matters to CISOs: A design-level RCE flaw in the Model Context Protocol — increasingly adopted for AI tool integration — threatens the AI supply chain and demands immediate review of any MCP implementations in your environment.

📖 Read full article

Jordan: Someone just built malware specifically to mess with Israel's water supply. Not power grids, not financial systems — water. Desalination plants. The infrastructure that keeps people alive in an arid region. That's where we are on a Monday morning. Welcome to Cleartext.

Alex: Good morning. I'm Alex Chen, and with me as always is Jordan Reeves. Today we're covering a lot of ground — OT attacks on critical infrastructure, a design-level RCE flaw threatening the AI supply chain, a breach at Vercel that's a case study in third-party AI risk, a guilty plea from Scattered Spider, AI-powered voice phishing going turnkey, and global finance officials sounding alarms about AI outpacing regulatory frameworks. Busy day. Let's get into it.

Jordan: ZionSiphon is the lead, and it deserves to be. Darktrace researchers identified purpose-built malware targeting Israeli water treatment and desalination OT systems. We're talking about malware engineered for a specific industrial environment — it establishes persistence, tampers with configuration files, and scans for OT-relevant services on the local subnet. This isn't commodity malware repurposed for ICS. Someone spent real time and resources building this for one target type.

Alex: And for CISOs running OT environments, that specificity is exactly what should keep you up at night. The threat model has shifted. The question is no longer whether sophisticated actors will target industrial control systems — it's whether your segmentation and monitoring would even detect something this tailored. Most OT networks still have inadequate east-west visibility. If ZionSiphon is scanning the subnet, it needs to be somewhere it can do that. That means your segmentation assumptions may be wrong.

Jordan: The geopolitical context here is obvious — this is the Middle East conflict extending into cyber-physical space. But the operational lesson transcends the geography. Attacks on water infrastructure are not new — Oldsmar, Florida in 2021 was a wake-up call that most people snoozed through. What's different now is the sophistication. Config file tampering in OT systems can have consequences that don't manifest for hours or days after the attacker is long gone. By the time you see the effects, you've lost the forensic window.

Alex: The board conversation here is straightforward: cyber-physical incidents are liability events, not just security events. If you have OT in your environment — manufacturing, utilities, building systems, doesn't matter — and you can't answer basic questions about segmentation, monitoring coverage, and incident response playbooks specific to those systems, that's a governance gap with real legal exposure.

Jordan: Staying on the geopolitical thread, let's talk about what came out of Washington last week. Global finance officials — we're talking IMF-level conversations — issued formal warnings that advanced AI models are accelerating vulnerability discovery and exploitation faster than regulators can respond. That's not a think tank white paper. That's finance chiefs publicly acknowledging that AI is breaking their regulatory timeline assumptions.

Alex: This matters to CISOs for a specific reason: it gives you board-level credibility when you're making the case for proactive AI governance investment. When the IMF is saying the gap between AI-driven threat acceleration and regulatory response is widening, your CFO can't argue that the risk is theoretical. The counter-argument to investing in AI security controls just got weaker.

Jordan: And it's not abstract. Let's talk about ATHR. This is an AI-powered voice phishing platform available right now for four thousand dollars and a cut of whatever the criminals take. One operator runs fully automated vishing campaigns. The platform spoofs alert emails from Google, Microsoft, Coinbase — embeds a callback number — and when the victim calls, an AI voice agent handles the entire interaction. No human required until there's money to collect.

Alex: Four thousand dollars. That's the price of entry for a sophisticated, scalable social engineering operation. The talent requirement is gone. The scale requirement is gone. This is a direct threat to any organization that still treats phone-based authentication or help desk callbacks as a security control. And that is most organizations. Scattered Spider — which we'll come back to — used manual social engineering to breach some of the biggest names in hospitality. Now that playbook is automated and available to anyone with the startup capital of a used car.

Jordan: The action item here isn't complicated but it is urgent: your help desk needs to be operating with zero-trust assumptions on voice interactions. No resets, no credential handoffs, no exceptions based on a convincing caller. If you don't have out-of-band verification that's genuinely independent of the channel the caller is using, you have a gap that ATHR will find.

Alex: On Scattered Spider — Tyler Buchanan pleaded guilty Friday to wire fraud conspiracy and aggravated identity theft. At least eight million in cryptocurrency. This group hit MGM and Caesars with social engineering so effective it caused hundreds of millions in losses. Law enforcement catching up is meaningful, but the techniques they pioneered are now table stakes for criminal groups operating at much lower sophistication levels. The guilty plea closes a chapter. It doesn't close the threat.

Jordan: Now let's talk about the Vercel breach, because this one is a preview of what the next two years of supply chain risk looks like. Vercel's breach didn't originate in Vercel's systems. It originated in Context.ai — a third-party AI tool one of their employees was using. Attacker compromised Context.ai, pivoted into that employee's Google Workspace account, and from there into internal Vercel systems. ShinyHunters is claiming credit and trying to sell the data.

Alex: This is the AI tool sprawl problem made concrete. The average enterprise employee is now using anywhere from five to fifteen AI tools — some sanctioned, many not. Each of those tools is an OAuth connection, a data pipeline, a trust relationship that your security team probably didn't review and almost certainly isn't monitoring. Context.ai isn't some obscure tool — it's used by engineering teams at well-known companies. The attack surface here scales with AI adoption, and right now AI adoption is outpacing any governance framework most organizations have in place.

Jordan: The immediate ask for your teams: inventory the AI tools employees are using, not just the ones IT approved. Look at OAuth grants across your Google and Microsoft environments. Anything with broad permissions from a third-party AI service is a potential pivot point. Revoke what you can't justify.

Alex: And speaking of AI supply chain risk, the MCP vulnerability from this morning demands attention. Researchers found a critical design-level flaw in Anthropic's Model Context Protocol — MCP is the emerging standard for connecting AI models to external tools and data sources. This isn't a bug that gets patched in the next release. It's an architectural weakness that enables remote code execution on any system running a vulnerable MCP implementation. And MCP adoption is growing fast.

Jordan: "By design" flaws are the hardest category. There's no CVE patch cycle that fixes this cleanly. If you have engineering teams building on MCP — and increasingly they are — you need to understand your blast radius now. This is the kind of vulnerability that becomes a supply chain incident at scale before most organizations realize they're even exposed.

Alex: Let's close with Europe before the outlook. The EU awarded a €180 million cloud services tender to four European providers — OVHcloud, CleverCloud, STACKIT, Scaleway, Proximus. This is the EU institutionalizing cloud sovereignty in a very concrete way. For multinational CISOs, this is a signal, not just a procurement story. Data residency requirements tied to EU operations are going to tighten, and the assumption that your US hyperscaler footprint cleanly covers European regulatory obligations is increasingly fragile.

Jordan: What's the thread this week? Everything we've covered today has a common denominator: the attack surface is expanding faster than organizational governance is adapting. ZionSiphon is targeting gaps in OT monitoring. ATHR is targeting gaps in voice authentication. Context.ai-to-Vercel is targeting gaps in AI tool oversight. MCP is targeting gaps in AI architecture review. The finance officials in Washington are worried about regulatory frameworks failing to keep pace. That's not coincidence — that's the operating environment.

Alex: The CISOs who are going to be in the strongest position twelve months from now are the ones who this week pick two or three of those gaps and actually close them. Not commission a working group. Not add it to the risk register. Close them. Board-level pressure on AI risk is real and growing. The ATHR story gives you a concrete, low-cost threat example that any audit committee will understand. Use it.

Jordan: Watch for MCP-related disclosures to accelerate. The research community has been looking at AI protocol security hard for the last six months, and ZionSiphon copycat variants targeting OT environments outside the Middle East are a legitimate concern for anyone in critical infrastructure globally.

Alex: That's Cleartext for Monday, April 20th. We'll be back tomorrow. If this episode was useful, share it with someone on your team who needs the brief. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Stay sharp.

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

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 17 stories across 5 topic areas, including: Sweden blames Russian hackers for attempting ‘destructive’ cyberattack on thermal plant; ZionSiphon malware designed to sabotage water treatment systems; US nationals sentenced for aiding North Korea’s tech worker scheme.

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

Why it matters to CISOs: Russia-attributed destructive attacks on European energy infrastructure signal escalation beyond espionage — CISOs in critical infrastructure must update threat models for destructive OT attacks.

📖 Read full article

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

Why it matters to CISOs: Purpose-built OT malware targeting water treatment represents a maturation of the ICS threat landscape — CISOs with OT environments must assume they face bespoke, sector-specific malware, not just repurposed IT tools.

📖 Read full article

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

Why it matters to CISOs: Sentencing of Americans who ran laptop farms for DPRK operatives at 100+ companies underscores that the insider threat from fake remote workers is real and prosecutable — CISOs need robust identity verification for remote hires.

📖 Read full article

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

Why it matters to CISOs: The W3LL takedown dismantles a major phishing-as-a-service platform — CISOs should use this as a reminder that off-the-shelf phishing kits dramatically lower the barrier for credential theft at scale.

📖 Read full article

The Hacker News · Apr 17 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: The scale of Operation PowerOFF — 53 domains, 75K+ users, 3M accounts — demonstrates the industrialization of DDoS-for-hire and reinforces the need for resilient DDoS defenses.

📖 Read full article

The Hacker News · Apr 15 · Relevance: █████████░ 9/10

Why it matters to CISOs: OpenAI and Anthropic are now in direct competition for security-focused frontier AI — CISOs must evaluate which models their teams and vendors adopt, and understand the asymmetric risk of these same capabilities being used offensively.

📖 Read full article

Ars Technica Security · Apr 14 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Anthropic's Mythos is the first AI model to complete a difficult multistep infiltration challenge — CISOs should assume adversaries will gain access to similar capabilities and that exploit development timelines are compressing dramatically.

📖 Read full article

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

Why it matters to CISOs: Microsoft assigning CVEs to prompt injection in agentic platforms signals that AI agent vulnerabilities are now part of formal vulnerability management — CISOs deploying AI agents inherit an entirely new vulnerability class requiring runtime controls.

📖 Read full article

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

Why it matters to CISOs: Global finance officials formally acknowledging that AI-accelerated cyber risk outpaces regulatory guardrails gives CISOs ammunition for board conversations about increased security investment.

📖 Read full article

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

Why it matters to CISOs: Tyler Buchanan's guilty plea is a significant milestone in holding Scattered Spider accountable — CISOs can use this as evidence that social engineering-based intrusion groups face real legal consequences.

📖 Read full article

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

Why it matters to CISOs: A single vendor breach at Anodot cascading to a dozen+ enterprises including Rockstar Games illustrates the concentrated risk of SaaS supply chain dependencies — CISOs must map and stress-test critical vendor relationships.

📖 Read full article

The Hacker News · Apr 17 · Relevance: █████████░ 9/10

Why it matters to CISOs: NIST's decision to stop enriching most CVEs fundamentally changes how vulnerability management programs operate — CISOs must now identify alternative sources for CVE context, scoring, and prioritization data.

📖 Read full article

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

Why it matters to CISOs: ENISA becoming a Top-Level Root CNA signals a structural shift toward regional CVE governance — CISOs at multinationals need to track diverging vulnerability disclosure frameworks across jurisdictions.

📖 Read full article

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

Why it matters to CISOs: National Cyber Director signaling imminent executive orders on cyber strategy means CISOs — especially at federal contractors and critical infrastructure — should prepare for new compliance requirements.

📖 Read full article

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

Why it matters to CISOs: CISA internship cancellations and ongoing budget pressure signal a weakening federal cyber workforce pipeline — CISOs competing for talent should expect even tighter labor markets ahead.

📖 Read full article

The Hacker News · Apr 17 · Relevance: █████████░ 9/10

Why it matters to CISOs: Three zero-days in Microsoft Defender — the security tool itself — are being exploited in the wild with two still unpatched, meaning the defensive layer many orgs rely on is actively compromised and requires immediate compensating controls.

📖 Read full article

Krebs on Security · Apr 14 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Microsoft's second-largest Patch Tuesday ever (167+ CVEs including a SharePoint zero-day), combined with critical Adobe and Chrome zero-days, creates an extraordinary patching burden — CISOs need to prioritize and accept residual risk.

📖 Read full article

Jordan: This was the week the attack surface got a new address. Destructive malware targeting power grids and water treatment plants. Zero-days in the tool that's supposed to stop zero-days. And an AI arms race that global finance chiefs are now openly saying may outpace every regulatory guardrail we have. If you only pay attention to one theme this week, it's this: the infrastructure we built security on top of is no longer holding still.

Alex: Welcome back to Cleartext. I'm Alex Chen. It's Saturday, April 18th, and if you spent this week in board prep, travel, or just trying to keep your head above water, you're in the right place. This is our Week in Review — what mattered, what it means, and what you need walking into next week.

Jordan: And there was a lot that mattered.

Alex: There was. Here's what we're covering today. First, a geopolitical theme that has officially shifted from espionage to destruction — Russia and OT infrastructure, the ZionSiphon malware, and what it means that nation-state actors are now swinging for physical impact. Second, the AI security story got louder and more complicated this week — with new frontier models, a formal CVE assigned to a prompt injection flaw, and global finance officials publicly warning that AI is accelerating cyber risk faster than regulators can respond. Third, vulnerability management had a genuinely bad week — Microsoft's second-largest Patch Tuesday ever, and three zero-days in Microsoft Defender, two of which are still unpatched. And fourth, the CVE governance infrastructure is fracturing in ways that will affect every vulnerability management program you're running.

Jordan: Let's start with the story I think will look most significant in hindsight. On Tuesday, Sweden's civil defense minister publicly attributed a destructive cyberattack on a thermal power plant to Russian hackers. Not espionage. Not reconnaissance. Destructive intent against a heating facility. And the minister didn't hedge — she said Russian hackers are now attempting destructive cyberattacks against organizations across Europe.

Alex: The word "now" is doing a lot of work in that statement.

Jordan: It is. Because the shift from espionage to destruction is the escalation the OT security community has been warning about for years. And it landed the same week we got reporting on ZionSiphon — purpose-built malware targeting water treatment and desalination systems. This isn't repurposed IT tooling. This is bespoke, sector-specific malware designed specifically to sabotage operational technology environments.

Alex: And that distinction matters enormously from a threat modeling standpoint. A lot of OT security programs were built on the assumption that IT-origin malware would have to be adapted to cross into OT environments — that there would be some friction in that translation. ZionSiphon suggests adversaries have done that work. They've moved past adaptation into purpose-built tooling for specific critical infrastructure sectors.

Jordan: If you're a CISO in energy, water, utilities, transportation — your threat model needs to reflect that reality right now, not as a theoretical scenario. The question isn't whether your OT environment can be targeted. It's whether you have sufficient detection and response capability in that environment when the malware already knows exactly what it's looking for.

Alex: And on the insider threat side of geopolitics this week — the sentencing of two US nationals who ran laptop farms for North Korean operatives is worth a beat. Kejia Wang and Zhenxing Wang placed DPRK workers inside more than a hundred US companies. They got federal sentences. And the lesson for CISOs is simple: the fake remote worker problem is real, it's prosecutable, and if it happened at a hundred other organizations, the odds that some of your vendors or partners were in that pool are not trivial.

Jordan: The identity verification question for remote hires has never been more important. And the W3LL phishing-as-a-service takedown this week is a useful counterpoint — the FBI and Indonesian National Police dismantled that infrastructure, recovered credentials, disrupted twenty million dollars in fraud attempts. Law enforcement is landing punches. But the industrialization of attack tooling means every time one platform goes down, the barrier to rebuilding it is lower.

Alex: Let's move to AI, because this week the AI security story developed in two distinct and equally important directions simultaneously. On one hand, both OpenAI and Anthropic launched frontier models with explicit cybersecurity applications — GPT-5.4-Cyber and Claude Mythos respectively. On the other hand, Anthropic's Mythos became the first AI system to complete a difficult multistep infiltration challenge — and the UK's AI Security Institute published an assessment calling for security best practices in response.

Jordan: That's the tension you have to hold in your head. The same week OpenAI is expanding access for security teams, the UK government is documenting that the underlying model family just cleared a bar that, frankly, changes exploit development economics. The Cloud Security Alliance used the phrase "post-Mythos exploit storm" and I think that framing is going to stick. If adversaries get access to models with these capabilities — and they will — the timeline between vulnerability disclosure and weaponized exploit compresses dramatically.

Alex: And the board-level signal came from an unexpected source this week. Global finance officials meeting in Washington issued a formal warning that advanced AI models may rattle the global banking system — specifically that AI is speeding vulnerability discovery and exploitation faster than regulators can build guardrails. When the people who set financial stability policy start using language like that publicly, CISOs have a new asset in their budget conversations. You can walk into your board and say this isn't a security team concern anymore — the finance ministers of G7 nations are talking about it.

Jordan: Meanwhile, on the practical AI risk side — Microsoft had to assign a formal CVE to a prompt injection vulnerability in Copilot Studio. CVE-2026-21520, CVSS 7.5. The patch was deployed. And then Capsule Security found data could still exfiltrate post-patch. Both Microsoft and Salesforce patched prompt injection flaws in their agent platforms this week. The significance isn't the individual flaws — it's what CVE assignment signals. Prompt injection in agentic AI is now formally part of the vulnerability management surface. If you've deployed AI agents in your environment, you've inherited a new vulnerability class that your existing patch management program wasn't built to handle.

Alex: Runtime controls, agent behavior monitoring, trust boundaries in agentic workflows — these are now first-order security concerns, not future-state problems.

Jordan: Now let's talk about the week that broke vulnerability management. Microsoft's April Patch Tuesday was the second largest in the company's history — 167 CVEs, including a SharePoint zero-day. Adobe pushed an emergency patch for an RCE in Reader that has been actively exploited since November 2025. Google Chrome fixed its fourth zero-day of 2026. That's a patching burden that would stress any team under normal circumstances.

Alex: But the circumstances this week were not normal, because Huntress disclosed that three zero-days in Microsoft Defender itself are being actively exploited in the wild — BlueHammer, RedSun, and UnDefend — and as of Friday, two of the three remain unpatched. A researcher published proof-of-concept code in protest of Microsoft's researcher engagement practices. Whatever you think of the disclosure method, the operational reality is clear: the security tool a significant portion of enterprise environments rely on for endpoint protection is actively compromised with no patch available for the most critical vulnerabilities.

Jordan: That requires compensating controls right now. Behavioral monitoring, isolation of high-value endpoints, layered detection that doesn't depend on Defender alone. The assumption that your security tooling is a trusted layer needs to be interrogated this week.

Alex: And underneath all of this, the CVE governance infrastructure is quietly fracturing in ways that will have long-term operational consequences. NIST announced it will stop enriching the majority of CVEs — only those meeting specific criteria around critical software, federal systems, or active exploitation will get the context, scoring, and prioritization data that vulnerability management programs depend on. The trigger was a 263 percent surge in CVE submissions that overwhelmed NVD capacity.

Jordan: For most vulnerability management programs, NVD enrichment has been the assumed baseline. If that baseline goes away, you need alternative sources for context and scoring — commercial feeds, CISA's KEV catalog, vendor advisories. And you need to make those decisions now, not when you notice a gap.

Alex: Simultaneously, ENISA is pursuing top-level root CNA status, which would make it the third Top-Level Root CVE Numbering Authority alongside CISA and MITRE. Combined with NIST's retreat, what you're seeing is CVE governance fragmenting along geopolitical lines. Multinationals in particular need to start tracking that divergence, because the vulnerability disclosure frameworks you're compliant with in the US may not map cleanly to what's emerging in Europe.

Jordan: And on the regulatory pipeline — the National Cyber Director signaled executive orders are coming as the next step in national cyber strategy implementation. If you're a federal contractor or critical infrastructure operator, that means new compliance requirements are likely within months, not years. Get ahead of it now.

Alex: Let's take a step back before we close. Jordan, if you had to name the defining characteristic of this week — not the biggest story, but the theme that tied it all together — what is it?

Jordan: Compression. Every cycle that used to give defenders time is getting shorter. The time between vulnerability disclosure and exploitation. The time between a new AI capability and adversary access to it. The time between a vendor breach and extortion letters going out to a dozen of their customers. The week in security used to operate on timelines that gave thoughtful teams room to respond. That room is shrinking.

Alex: I'd put it slightly differently and say this was a week about the assumption stack. We assumed that our security tools were trustworthy — three Defender zero-days challenged that. We assumed NVD enrichment was a stable foundation — NIST changed that. We assumed nation-state OT threats had a ceiling — ZionSiphon and the Sweden thermal plant attack raised it. CISOs going into next week need to be honest about which assumptions in their security programs are load-bearing and whether those assumptions still hold.

Jordan: Prioritize the Defender compensating controls. Review your CVE enrichment sources before you discover a gap mid-incident. And if you have OT environments, this is the week to have a direct conversation with your operations leadership about whether your threat model reflects what we learned.

Alex: Walking into next week: watch for Microsoft's out-of-band patches for the two remaining Defender zero-days. Watch for movement on the National Cyber Director's executive order signals. And keep an eye on whether Mythos capabilities start showing up in threat actor tooling — that's the development that would change the calculus on everything else we discussed today.

Jordan: It's been a heavy week. But this is the job.

Alex: That's the Week in Review for the week ending April 18th, 2026. The daily show returns Monday — new stories, new analysis, same pace. If this episode was useful, share it with a peer who needed the catch-up. We'll see you Monday on Cleartext.

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

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 4 topic areas, including: US nationals sentenced for aiding North Korea’s tech worker scheme; ZionSiphon malware designed to sabotage water treatment systems; Ukrainian emergency services and hospitals hit by espionage campaign using new AgingFly malware.

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

Why it matters to CISOs: With sentences of 8-9 years for facilitating DPRK IT worker infiltration at 100+ US companies, this case underscores the insider threat from fraudulent remote workers and the need for robust identity verification in hiring pipelines.

📖 Read full article

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

Why it matters to CISOs: Purpose-built OT malware targeting water infrastructure signals escalating threats to critical infrastructure; CISOs in utilities and organizations with OT environments should review ICS segmentation and monitoring capabilities.

📖 Read full article

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

Why it matters to CISOs: State-sponsored espionage targeting hospitals and emergency services with novel malware highlights persistent threats to healthcare globally and the continued evolution of wartime cyber operations with potential spillover risk.

📖 Read full article

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

Why it matters to CISOs: AI-powered vishing at scale represents a step-change in social engineering risk; CISOs need to revisit help desk authentication procedures and employee awareness training to address fully automated voice phishing attacks.

📖 Read full article

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

Why it matters to CISOs: CISA operating at 40% staffing fundamentally degrades federal threat intelligence sharing and incident response support that enterprise security teams rely on, forcing CISOs to reassess their dependency on government cyber resources.

📖 Read full article

Cybersecurity Dive · Apr 16 · Relevance: ████████░░ 8/10

Why it matters to CISOs: NIST deprioritizing enrichment of most CVEs means vulnerability management programs that rely on NVD data for scoring and context will have significant gaps—CISOs must evaluate alternative intelligence sources and adjust patching workflows.

📖 Read full article

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

Why it matters to CISOs: A CVSS 9.8 flaw in Cisco Webex SSO certificate validation that allows user impersonation across the service demands immediate patching and customer action—particularly given Webex's ubiquity in enterprise communications.

📖 Read full article

Help Net Security · Apr 17 · Relevance: █████████░ 9/10

Why it matters to CISOs: Three unpatched zero-days in Microsoft Defender—the default endpoint protection for most enterprises—are now actively exploited, with one allowing complete disabling of Defender. CISOs must evaluate compensating controls and EDR layering immediately.

📖 Read full article

Jordan: Three zero-days in Microsoft Defender. All three being exploited right now. One of them lets a standard user turn Defender off entirely. No patch. Happy Friday.

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

Jordan: And I'm Jordan Reeves.

Alex: Today we've got a lot of ground to cover and it matters. Three unpatched Defender zero-days actively in the wild. CISA operating at 40% capacity and warning about it publicly. The federal vulnerability database quietly breaking. North Korean operatives embedded at over a hundred US companies, and the people who helped them just got sentenced to nearly a decade in prison. We'll also hit a new AI-powered vishing platform that's industrializing social engineering, a piece of OT malware purpose-built to sabotage water systems, and four critical Cisco patches including one that's a 9.8. Let's get into it.

Jordan: So the Defender zero-days. This is the lead for a reason. A researcher dropped a PoC earlier this month for a privilege escalation flaw in Microsoft Defender. This week, they came back with two more. The first new one, called RedSun, is another privilege escalation that gets you to SYSTEM level. The second, called UnDefend, lets a standard user block Defender from receiving signature updates entirely. Huntress has confirmed active exploitation of all three. There are no patches.

Alex: Let me be direct about the business impact here. Microsoft Defender is the default endpoint protection in most enterprise environments. When your EDR can be silenced by a standard user account, your entire detection and response capability is potentially gone before you even know an intrusion is happening. If you're running Defender as a standalone solution, that is a gap you need to close today. This is the argument for layered EDR. It's also the argument for having that conversation with your board not as a future initiative but as an emergency budget item this quarter. Talk to your vendors, look at compensating controls, and review what telemetry you have outside of Defender that would catch lateral movement if your endpoint protection is dark.

Jordan: Related note before we move on: Cisco patched four critical vulnerabilities this week across Identity Services and Webex. The one that stands out is CVE-2026-20184, CVSS 9.8, improper certificate validation in Webex SSO that allows an attacker to impersonate any user in the service. Cisco has said this one requires additional customer action beyond applying the patch. That's the phrase that should be jumping out at you. Pull the advisory, read the full remediation steps, don't assume patching is sufficient.

Alex: Now let's talk about CISA, because this one has systemic implications for every enterprise security team in this country. The acting director came out this week and publicly warned of what she called detrimental capacity impacts. CISA is operating at 40% staffing. Forty percent. The FY budget request is $2.5 billion, which tells you the scale of the strain they're acknowledging.

Jordan: Here's what that actually means operationally. CISA is the connective tissue for federal threat intelligence sharing. They run the advisories, they coordinate incident response for critical infrastructure, they operate the information sharing mechanisms that private sector security teams depend on. At 40% capacity, the cadence slows, the depth decreases, and response times stretch. The question every CISO should be asking is: how dependent is my program on that flow of government intelligence, and what's my plan if it degrades further?

Alex: This isn't political commentary. It's a resource planning conversation. The organizations that built their threat intelligence capability entirely on government feeds are more exposed right now than they should be. If you haven't already diversified into commercial threat intel, sector-specific ISACs, and direct vendor relationships, this is the moment that argument wins internally.

Jordan: Directly related: NIST announced this week that it's limiting vulnerability enrichment in the National Vulnerability Database. CVE submissions surged 263% and the NVD simply can't keep up. Going forward, they'll only enrich vulnerabilities that meet new prioritization criteria. Pre-March 2026 vulnerabilities will no longer receive NVD enrichment at all.

Alex: The NVD is the backbone of most commercial vulnerability management platforms. Scoring, CVSS data, patch context—a significant portion of that flows from NVD enrichment. If you have a vuln management program that's essentially a wrapper around NVD data, you now have gaps you can't see. This is the week to have a frank conversation with your vuln management vendor about where their data comes from and what their alternative enrichment strategy looks like. It's also the week to look at whether you're subscribed to CISA's KEV catalog as a parallel prioritization mechanism, because that's not going away.

Jordan: Alright, let's talk North Korea, because this week's sentencing is a useful data point in a broader threat picture. Two US nationals—Kejia Wang and Zhenxing Wang—got eight to nine years for running shell companies and laptop farms that helped DPRK IT operatives get hired at over a hundred US companies. The scheme generated more than five million dollars for the North Korean government.

Alex: What strikes me about this case is the infrastructure required. Shell companies. Physical laptop farms to make remote workers appear domestic. Intermediaries managing the persona maintenance. This isn't a few clever individuals with fake LinkedIn profiles. This is an organized, state-sponsored employment fraud operation at scale. And the fact that it penetrated over a hundred companies tells you that standard hiring checks are insufficient against a well-resourced adversary.

Jordan: The geopolitical context is that this revenue stream directly funds DPRK's weapons programs. These aren't just cybercriminals running a hustle. They're executing a state economic priority. Which means the program isn't going away because two facilitators got sentenced. The sentences are a deterrent signal to US-based enablers, but the DPRK side of this operation is unchanged.

Alex: Practical implication for your hiring pipeline: if you have remote contractors or vendors, especially in software development, your identity verification process needs to go beyond what a videoconference can tell you. Device fingerprinting, out-of-band verification, anomalous access pattern monitoring for new hires—these aren't paranoid. They're appropriate given what we now know happened at a hundred companies.

Jordan: Two more geopolitical items worth flagging. ZionSiphon is a new piece of OT-specific malware designed to sabotage water treatment and desalination systems. Purpose-built for operational technology disruption. If you have any OT environment or you have exposure through third-party suppliers who do, this is a signal about the direction of threat actor investment. ICS segmentation, network monitoring between IT and OT, and tabletop exercises that include OT disruption scenarios—not optional anymore.

Alex: And separately, Ukrainian hospitals and emergency services were hit with a new espionage campaign using malware called AgingFly. The spillover risk from wartime cyber operations into global healthcare infrastructure is real and documented. If you're in healthcare or you have European operations, that threat landscape is active and evolving.

Jordan: Finally, the ATHR vishing platform. This is a crimeware-as-a-service product that automates voice phishing using both human operators and AI voice agents. Fully automated credential harvesting via phone. The significance is commoditization. AI-powered vishing is no longer a sophisticated nation-state technique. It's a platform someone can rent.

Alex: Your help desk is the target. That's always been true, but now the scale and polish of the attack has increased dramatically. Out-of-band authentication for sensitive requests, callback verification protocols, and yes, updated security awareness training that specifically addresses AI voice impersonation—these need to be on the short list. The classic "my boss called and needs access reset" scenario just got a lot more convincing.

Jordan: So zooming out, the theme this week is infrastructure erosion. Not dramatic single breaches, but a systematic degradation of the foundations security teams rely on. CISA at 40%. NVD enrichment contracting. Microsoft's default endpoint tool sitting unpatched with active exploits. These aren't isolated incidents. They're cumulative stress on the ecosystem.

Alex: And the organizations that built resilient, redundant security capabilities—layered EDR, diversified intel sources, strong identity verification, hardened OT environments—those teams are better positioned to absorb these shocks. The ones that outsourced their thinking to a single government feed or a single endpoint tool are finding out why that was a risk. The board conversation this quarter isn't about new threats. It's about whether your foundation is solid enough to handle the ones you already knew about.

Jordan: Watch the Microsoft Defender patch timeline. Watch CISA's budget negotiation. And watch whether the ATHR platform starts showing up in incident reports, because that will be the signal it's gone mainstream.

Alex: That's Cleartext for Friday, April 17th. If this was useful, share it with a peer. We'll be back Monday. Stay sharp.

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

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: Sweden blames Russian hackers for attempting ‘destructive’ cyberattack on thermal plant; Two US nationals jailed over scheme that generated $5 million for the North Korean regime; UK warns businesses to address cyber risks amid Anthropic AI panic.

TechCrunch Security · Apr 15 · Relevance: █████████░ 9/10

Why it matters to CISOs: Russian state-sponsored destructive attacks on European critical infrastructure signal escalating cyber operations that could target energy and industrial sectors globally, requiring CISOs to reassess OT/ICS defenses.

📖 Read full article

Help Net Security · Apr 16 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Prison sentences for US facilitators of North Korean IT worker fraud schemes underscore the insider threat risk from fraudulent remote employees and the need for robust identity verification in hiring processes.

📖 Read full article

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

Why it matters to CISOs: Government-level warnings about frontier AI models reshaping the threat landscape signal that regulators expect enterprises to proactively adapt defenses, and boards will be asking CISOs about AI-augmented threat preparedness.

📖 Read full article

VentureBeat Security · Apr 15 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Microsoft assigning CVEs to prompt injection flaws in agentic AI platforms signals a new vulnerability class CISOs must track, as every enterprise deploying AI agents now inherits prompt injection risk requiring formal remediation workflows.

📖 Read full article

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

Why it matters to CISOs: A Salesforce environment breach exposing 13.5 million accounts highlights the persistent risk of SaaS platform compromises and the need for robust third-party SaaS security controls.

📖 Read full article

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

Why it matters to CISOs: Forthcoming executive orders implementing the national cyber strategy could impose new compliance obligations on enterprises, particularly around software supply chain security and incident reporting.

📖 Read full article

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

Why it matters to CISOs: NIST's decision to only enrich CVEs for critical software, federal systems, and actively exploited flaws fundamentally changes how enterprise vulnerability management programs source enrichment data, requiring CISOs to diversify their intelligence feeds.

📖 Read full article

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

Why it matters to CISOs: A $70M Series A for an AI-driven SIEM alternative led by a former Amazon GuardDuty leader signals significant investor confidence in agentic AI for detection and response, potentially reshaping the SIEM market CISOs depend on.

📖 Read full article

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

Why it matters to CISOs: Active exploitation of CVE-2026-33032 (CVSS 9.8) in nginx-ui enables full server takeover without authentication; enterprises running nginx management interfaces need immediate patching.

📖 Read full article

Jordan: Sweden just publicly blamed Russia for attempting a destructive cyberattack on a thermal plant. Not espionage. Not data theft. Destructive. That word is doing a lot of work, and it should have every CISO with OT exposure paying close attention this morning.

Alex: This is Cleartext. Thursday, April 16th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. On today's show: Russian destructive operations targeting European critical infrastructure, what two prison sentences tell you about your hiring process, the CVE that signals a whole new vulnerability class in your AI stack, and why NIST just quietly changed how your vuln management program works — whether you noticed or not. Let's get into it.

Alex: So Jordan, Sweden. The civil defense minister standing up and saying Russian hackers are now attempting destructive cyberattacks against European organizations. That framing is deliberate.

Jordan: Extremely deliberate. Attribution at the ministerial level is a policy decision, not just an intelligence one. Sweden is signaling something. And the word "destructive" is significant because it distinguishes this from the years of Russian cyber operations that were primarily about intelligence collection or pre-positioning. This was an attempt to cause physical consequence — in this case, to a thermal plant's operational technology. That's a different category of threat.

Alex: For CISOs in energy, utilities, manufacturing — any sector with OT or ICS exposure — the question you need to be asking isn't whether your IT environment is hardened. It's whether your operational technology sits behind a meaningful security boundary from that IT environment. In most organizations, the honest answer is still no.

Jordan: And the attack surface has gotten worse over the past few years because of remote monitoring, cloud-connected OT, digital twin infrastructure. All of that connectivity that makes operations more efficient also makes it easier for someone to reach the thermal controls. The Purdue model isn't dead, but it needs to be actively enforced, not assumed.

Alex: This is a board conversation. If you're a CISO at an organization with physical infrastructure — energy, water, healthcare facilities, manufacturing — you need to be able to answer whether a nation-state could cause a physical outage from a cyber intrusion. If you can't answer that with confidence, that's your priority this quarter.

Jordan: And don't wait for your sector to be the named target. Sweden today. The Baltic states last year. Russia does not distinguish between NATO members and partners when it comes to infrastructure pressure campaigns.

Alex: Let's pivot to a story that feels different on the surface but hits a very similar nerve for a lot of organizations. North Korean IT worker fraud. Two US nationals sentenced — 108 and 92 months respectively — for running a scheme that placed DPRK workers inside over a hundred American companies, including Fortune 500 firms, using stolen identities. The operation generated five million dollars for the North Korean government.

Jordan: This has been a persistent threat for three years now, and it keeps scaling. What's notable here is the prosecution of the facilitators — the US nationals who ran the laptop farms and handled the identity laundering. That's the supply chain of this operation getting disrupted. But it doesn't stop the demand side, which is DPRK's ongoing need to generate hard currency.

Alex: From a CISO perspective, the insider threat angle here is underappreciated. These weren't hackers breaking in. They were on your payroll, with access to your systems, your code, your IP — sometimes for months. The identity verification problem in remote hiring is real, and it's not an HR problem, it's a security program problem.

Jordan: The practical controls are live video verification during hiring, device attestation requirements before network access, behavioral analytics once someone's in. But honestly, the companies that got burned were largely not thinking about their hiring pipeline as an attack surface. That mindset shift still hasn't happened broadly.

Alex: It needs to. Especially for any company hiring remote contractors in software development, cloud infrastructure, or anything touching sensitive systems. Okay, two governance stories that I want to cover together because they both reshape the compliance and vulnerability management landscape.

Jordan: Start with NIST because that one has immediate operational impact.

Alex: Agreed. NIST announced that the National Vulnerability Database will now only enrich CVEs for critical software, systems used by the federal government, and vulnerabilities under active exploitation. Everything else — pre-March 2026 vulnerabilities included — no longer gets that enrichment. This is a resource decision driven by the sheer volume of CVEs overwhelming NIST's capacity.

Jordan: And it's a problem that's been building for two years. But here's the practical consequence: if your vulnerability management program was relying on NVD enrichment as its primary source of severity context, you now have a gap. You need to diversify your intel feeds — CISA KEV, vendor advisories, commercial threat intel sources. NVD alone is no longer sufficient.

Alex: On the executive order front — National Cyber Director Sean Cairncross confirmed this week that the national cyber strategy is moving forward actively, with executive orders as the likely implementation mechanism. Watch for impacts on software supply chain security requirements and incident reporting obligations, particularly if you're in a regulated industry or touch federal contracts.

Jordan: The supply chain piece is the one I'd prioritize tracking. Post-XZ Utils, post-SolarWinds, there's genuine appetite in policy circles to impose real requirements on how software is built and verified. That will land on CISOs, not just their vendors.

Alex: McGraw Hill. ShinyHunters leaked data from 13.5 million user accounts. The breach vector was their Salesforce environment. This is a story we've seen before — different company, same vector.

Jordan: ShinyHunters is consistent. They go after SaaS environments, particularly Salesforce. The question for every CISO is: what does your Salesforce environment contain, who has access to it, and are you monitoring for abnormal data access or export activity? Most organizations treat Salesforce as a business application, not as a data store requiring security controls. That's the gap.

Alex: Third-party SaaS posture management is not optional anymore. The McGraw Hill breach affects 13.5 million people. The reputational and regulatory exposure from that is significant. Build that SaaS security layer into your program.

Jordan: Quick takes now. Microsoft assigned CVE-2026-21520 — CVSS 7.5 — to a prompt injection flaw in Copilot Studio. The patch is deployed. But the story here isn't the patch, it's the precedent. Microsoft assigning a CVE to an agentic AI platform is, as Capsule Security noted, highly unusual. It signals that prompt injection is now a formal vulnerability class, not just a research curiosity.

Alex: Which means if you're running AI agents — Copilot, Salesforce Agentforce, anything with autonomous action capability — you need a prompt injection assessment in your security review process. Your AI vendors should be answering questions about their injection mitigations the same way they answer questions about auth and encryption.

Jordan: Nginx UI. CVE-2026-33032. CVSS 9.8. Actively exploited. Full server takeover without authentication. If you're running nginx management interfaces with MCP support, patch now. Don't schedule it. Don't queue it. Now.

Alex: Artemis — $70 million Series A, founded by the former Amazon GuardDuty product lead, building an AI-driven SIEM alternative. Worth watching. The fact that Felicis is leading at that size for a SIEM challenger says investors believe the legacy SIEM market is genuinely disruption-ready. We'll see if the technology delivers.

Jordan: The SIEM market has needed disruption for a decade. Agentic telemetry correlation is a compelling pitch. I'd want to see how it handles noisy enterprise environments before pulling any incumbent contracts.

Alex: So stepping back — what's the theme of this week?

Jordan: Convergence of threat surfaces. You have Russian state actors going after physical infrastructure through OT. You have North Korean intelligence operations running through your HR pipeline. You have AI platforms introducing vulnerability classes that your existing security frameworks weren't built to handle. And the regulatory infrastructure that's supposed to help — NVD, compliance frameworks — is straining under volume and velocity.

Alex: The common thread for me is that the perimeter keeps expanding in unexpected directions. OT networks, hiring pipelines, AI agent contexts — none of these were primary attack surfaces ten years ago. The CISO role is fundamentally about being ahead of that expansion, and right now the expansion is faster than most programs can absorb.

Jordan: What to watch next: any escalation in European critical infrastructure targeting as we head into summer. The Russia-Ukraine dynamic has historically driven more aggressive cyber operations during warmer months. And watch for the first executive order under the new cyber strategy — that will set the compliance agenda for the next two years.

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

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

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 Workers Recalled Despite Shutdown; Sweden says pro-Russian hackers attempted to breach thermal power plant; We’re only seeing the tip of the chip-smuggling iceberg.

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

Why it matters to CISOs: A CISA funding lapse directly impacts the federal cyber defense posture and could degrade threat intelligence sharing, vulnerability coordination, and incident response support that enterprise security teams rely on.

📖 Read full article

The Record (Recorded Future) · Apr 15 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Pro-Russian targeting of Western critical infrastructure signals continued escalation that CISOs in energy, utilities, and adjacent sectors must factor into threat models and OT security strategies.

📖 Read full article

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

Why it matters to CISOs: AI chip smuggling networks and shadow data centers across Southeast Asia raise supply chain integrity and sanctions compliance concerns for CISOs whose organizations source hardware or operate in affected regions.

📖 Read full article

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

Why it matters to CISOs: The release of GPT-5.4-Cyber in competition with Anthropic's Mythos signals a new class of AI tools purpose-built for security operations; CISOs should evaluate how these models fit into defensive workflows while assessing dual-use risks.

📖 Read full article

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

Why it matters to CISOs: Former Black Basta affiliates are reusing proven social engineering tactics at scale against enterprises; CISOs need to ensure their SOCs are tuned to detect these TTPs and that executive-targeted phishing defenses are current.

📖 Read full article

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

Why it matters to CISOs: A Salesforce misconfiguration leading to a breach and extortion underscores the persistent risk of SaaS misconfigurations as a top attack vector — a direct concern for any CISO managing sprawling cloud environments.

📖 Read full article

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

Why it matters to CISOs: With only 34% of cybersecurity professionals planning to stay in their current roles, CISOs face acute workforce retention risk that directly impacts program continuity and institutional knowledge.

📖 Read full article

Krebs on Security · Apr 14 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A SharePoint zero-day actively exploited in the wild, a publicly disclosed Windows Defender weakness, Chrome's fourth zero-day of 2026, and an emergency Adobe Reader RCE flaw demand immediate patching prioritization across enterprise environments.

📖 Read full article

Jordan: CISA just recalled furloughed workers to their desks — without a funding resolution in sight. That's not a normal government budget story. That's the federal cyber safety net operating in legal and financial limbo while adversaries are watching.

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

Jordan: And I'm Jordan Reeves.

Alex: Today's show: the CISA funding situation and what it actually means for your threat intelligence pipeline. Pro-Russian hackers hit a Swedish power plant — what that signals for OT security teams in the West. Black Basta's playbook is back, and it spiked last month. April Patch Tuesday is a heavy lift. And OpenAI enters the purpose-built cyber model race. A lot of ground to cover. Let's get into it.

Jordan: So CISA. Here's what we know: DHS ordered furloughed personnel back to work despite an unresolved congressional funding standoff. That sounds like good news on the surface. Workers are back. Lights are on. But the underlying dynamic should concern any CISO who relies on federal threat intelligence pipelines, because what you have is an agency operating under legal ambiguity, with staff who haven't been paid reliably, and no certainty about when that resolves. That degrades institutional focus in ways that don't show up on a dashboard.

Alex: And the downstream effects are real and specific. We're talking about CISA's vulnerability coordination function, their threat sharing programs, the support they provide during significant incidents. If you're a critical infrastructure operator — financial services, energy, healthcare — and you've built CISA responsiveness into your incident response playbook, this is the moment to pressure-test that assumption. What's your fallback if CISA's capacity is degraded during a major event?

Jordan: The other thing worth saying plainly: adversaries read the news. A publicly visible disruption to the federal cyber apparatus is a signal. Not that it triggers attacks by itself, but it factors into adversary calculus on timing and target selection.

Alex: Which connects directly to the Sweden story. Swedish defense officials confirmed that a pro-Russian group attempted to disrupt a thermal power plant in western Sweden — targeting operational technology, and this happened last year. The disclosure now is notable in itself.

Jordan: A few things here for CISOs in energy and utilities, and honestly anyone adjacent to critical infrastructure. First, the geographic expansion of Russian-aligned targeting continues. This isn't new doctrine, but it is accelerating. Sweden as a NATO entrant is a meaningful target set. Second, OT environments remain the soft underbelly. The attack surface between corporate IT and operational technology — that convergence zone — is where these groups are probing. If your OT security strategy is still primarily air-gap mythology, this is a wake-up call.

Alex: And for boards that keep asking whether geopolitical risk is really a security budget line item — Sweden is your answer. This isn't hypothetical threat modeling. It's a confirmed attempt to disrupt physical infrastructure using cyber means.

Jordan: Let's shift to the Black Basta affiliate campaign, because this one is operationally immediate. ReliaQuest tracked a social engineering intrusion campaign that spiked in March, has been running since at least May 2025, and is being operated by former Black Basta affiliates carrying the playbook forward. Dozens of organizations targeted.

Alex: The reason this matters beyond the headline numbers is the word "former." Black Basta as a brand is degraded — their internal chat logs leaked, their infrastructure disrupted. But the affiliates who built their skills inside that operation didn't disappear. They regrouped. They're running fast-scale intrusions using proven social engineering TTPs against enterprises. This is what happens when you disrupt the top of a ransomware hierarchy without addressing the talent base underneath.

Jordan: The specific TTPs are executive-targeted phishing and help desk manipulation. Those two vectors together tell you something important: they're going around technical controls by targeting human decision points. Your EDR doesn't catch a help desk agent resetting MFA for someone who sounds authoritative on the phone.

Alex: So the action items here are concrete. Review your help desk identity verification procedures — specifically the exception handling paths for MFA resets and account recovery. Make sure your SOC has ReliaQuest's published indicators loaded. And if you haven't run a tabletop on social engineering at the executive layer recently, schedule it this quarter.

Jordan: McGraw-Hill is a good pivot to SaaS risk. Hackers exploited a Salesforce misconfiguration, accessed internal data, and then extorted the company. McGraw-Hill confirmed it. This is not a sophisticated nation-state attack. This is basic configuration hygiene failure leading to a breach and a public extortion event.

Alex: And the reason it keeps happening is organizational. In most enterprises, Salesforce is owned by sales operations or marketing. Security has advisory input at best. The team that configured the environment didn't have security as a first-order concern, and the security team didn't have visibility into what was exposed. That gap — between SaaS ownership and security oversight — is where these incidents are born. CISOs need formal SaaS security posture management, not periodic audits. Continuous monitoring of configuration drift in Salesforce, Workday, ServiceNow, and the rest of the stack.

Jordan: Patch Tuesday. April 2026 is a heavy one. Microsoft pushed fixes for 167 vulnerabilities. The two that demand immediate action: a SharePoint Server zero-day that is actively exploited in the wild, and BlueHammer, a publicly disclosed weakness in Windows Defender. Publicly disclosed means exploit code is available or incoming. Treat it accordingly.

Alex: Chrome is on its fourth zero-day of 2026. That is a meaningful trend line. And Adobe Reader has an emergency patch for an RCE flaw that's been actively exploited since at least November 2025. That means if you've been on a standard patching cadence, you've had exposure for months. The SharePoint zero-day and Adobe Reader RCE are your top priorities. Get those into emergency patch cycles today if they're not already in motion.

Jordan: OpenAI's GPT-5.4-Cyber. They're entering the purpose-built security model race directly against Anthropic's Mythos. They're extending access to verified security teams through something called the Trusted Access for Cyber program, and they're claiming internal safeguards and trust signals prevent misuse.

Alex: Let me be direct about where I land on this. The capability is real and the use cases for defensive security operations — threat hunting, alert triage, vulnerability analysis — are legitimate. But "trust signals prevent misuse" is a marketing claim, not a security architecture. The dual-use risk on a purpose-built cyber model is higher than a general-purpose LLM, because you're taking a model specifically tuned for offensive and defensive reasoning and making it more broadly available. CISOs evaluating these tools should be pressing vendors hard on what the verification actually means, what the audit trail looks like, and what the liability framework is if the model is used in a downstream attack.

Jordan: And watch the competitive dynamic. When two major AI labs are racing to capture security team adoption, procurement decisions get accelerated. Don't let vendor urgency outpace your evaluation process.

Alex: Let's close with the broader pattern this week is pointing toward. What we're seeing is a stress test of institutional reliability across multiple layers simultaneously. CISA is operating in funding limbo. The federal threat intel apparatus is uncertain. Adversaries — Russian-aligned groups specifically — are actively probing Western critical infrastructure OT environments. And domestically, a new IANS report out this week puts only 34% of cybersecurity professionals planning to stay in their current roles over the next twelve months. That's not a workforce retention footnote. That's an institutional knowledge crisis in slow motion.

Jordan: If two-thirds of your security team is considering leaving in the next year, your program continuity risk is significant regardless of your tooling investments. The humans who know your environment, your threat model, your vendor relationships — that institutional memory doesn't transfer easily. CISOs need to be having honest conversations with their leadership about compensation, scope, and career trajectory for security staff. The market is signaling something and it isn't being heard loudly enough in most boardrooms.

Alex: What I'm watching heading into next week: whether Congress moves on CISA's funding before the operational impact becomes visible in incident response timelines. And whether the Black Basta affiliate campaign expands its targeting — ReliaQuest's data suggests it's still accelerating.

Jordan: I'm watching the OT threat landscape in NATO-adjacent countries. The Sweden disclosure is likely the visible fraction of a larger pattern. Expect more to surface.

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

Jordan: Stay sharp.

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

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 5 topic areas, including: APT41 Delivers 'Zero-Detection' Backdoor to Harvest Cloud Credentials; FBI takedown of W3LL phishing service leads to developer arrest; CSA: CISOs Should Prepare for Post-Mythos Exploit Storm.

Dark Reading · Apr 13 · Relevance: █████████░ 9/10

Why it matters to CISOs: APT41's new backdoor targeting AWS, Azure, GCP, and Alibaba cloud credentials with zero AV detection signals an escalation in Chinese state-sponsored cloud compromise—CISOs must audit cloud IAM and credential hygiene immediately.

📖 Read full article

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

Why it matters to CISOs: The W3LL takedown dismantles a major phishing-as-a-service platform that bypassed MFA at scale—CISOs should review whether their organizations were targeted and reassess phishing-resistant authentication controls.

📖 Read full article

Dark Reading · Apr 13 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The Cloud Security Alliance's formal warning about AI-driven vulnerability discovery at scale gives CISOs a framework to brief boards on why patch management and assume-breach strategies need immediate investment.

📖 Read full article

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

Why it matters to CISOs: A supply-chain compromise of the popular Axios open-source library that impacted OpenAI's Mac applications highlights the persistent risk of dependency poisoning—CISOs should verify software composition analysis coverage for AI tooling.

📖 Read full article

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

Why it matters to CISOs: A supply-chain breach at cloud analytics provider Anodot cascading to 12+ enterprise customers including Rockstar Games underscores the criticality of third-party vendor risk assessments and data-sharing agreements.

📖 Read full article

Help Net Security · Apr 14 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A breach at a major global travel platform affecting reservation data (names, emails, phone numbers) is a reminder for CISOs to assess third-party travel and expense platform risk and monitor for social engineering follow-on campaigns targeting employees.

📖 Read full article

Help Net Security · Apr 14 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Nearly 29 million secrets leaked in public GitHub repos in 2025—a 34% YoY jump driven by AI agent credentials—demands CISOs implement secrets management governance specifically for AI/ML service accounts and integrations.

📖 Read full article

BleepingComputer · Apr 13 · Relevance: █████████░ 9/10

Why it matters to CISOs: An Adobe Acrobat/Reader zero-day (CVE-2026-34621) exploited via malicious PDFs since December is a high-urgency patch for virtually every enterprise—CISOs should push emergency deployment and scan for indicators of compromise.

📖 Read full article

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

Why it matters to CISOs: A critical SQL injection in Fortinet FortiClient EMS (CVSS 9.1) is now on CISA's KEV list with confirmed active exploitation—CISOs running Fortinet EMS must treat this as an emergency patch cycle.

📖 Read full article

Jordan: APT41 just dropped a backdoor with zero antivirus detections targeting your AWS, Azure, GCP, and Alibaba Cloud credentials simultaneously. If that sentence doesn't make you put down your coffee, I don't know what will.

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

Jordan: And I'm Jordan Reeves.

Alex: Today we have a dense one. APT41's new cloud credential harvester, the FBI taking down a major phishing-as-a-service operation, an Adobe zero-day that's been burning since December, a Fortinet critical at CVSS 9.1, and a supply-chain breach at Anodot that's got ShinyHunters extorting Rockstar Games and a dozen other enterprise names. We'll also get into the CSA's AI vulnerability storm warning and what 29 million leaked secrets in a single year actually means for how you're managing AI agent credentials. A lot to get through. Let's move.

Jordan: Let's start with APT41, because this is the story that should be sitting in front of your board before the end of the week. The group — China-state-sponsored, prolific, financially and espionage-motivated simultaneously — has deployed a new backdoor that is currently achieving zero antivirus detections. Not low detections. Zero. And it is purpose-built to harvest credentials across AWS, Google Cloud, Azure, and Alibaba Cloud in the same campaign. The C2 traffic is disguised through typosquatting domains, which means your network monitoring tools are likely going to miss it unless you're doing something more sophisticated than signature matching.

Alex: The business implication here is straightforward and severe. Cloud credentials are the keys to your kingdom. This isn't an attacker trying to get a foothold on a single endpoint — this is someone going directly for the identity layer of your entire cloud infrastructure. If they get valid IAM credentials, they can exfiltrate data, pivot laterally, spin up resources, and cover their tracks, all within your own environment's legitimate API calls. The detection problem is real. Traditional AV is useless here. What you need immediately is an audit of your cloud IAM posture — who has what, what's over-permissioned, where are credentials stored, are you rotating them, and do you have behavioral anomaly detection on your cloud control planes.

Jordan: And the Alibaba Cloud targeting is worth noting specifically. This tells you APT41 is operating globally and thinking about supply chain access — companies with Chinese market presence or partners using Alibaba Cloud infrastructure are now explicitly in scope. This isn't a US-only problem.

Alex: From APT41 to a different kind of adversary operation — the FBI and Indonesian authorities have taken down the W3LL phishing-as-a-service platform and arrested the alleged developer. W3LL is significant because it was industrialized MFA bypass. Seventeen thousand victims, over twenty million dollars in fraud attempts, and the platform was specifically engineered to intercept MFA tokens in real time. The reason this matters to your organization even after the takedown is twofold. First, check whether you were targeted — the FBI will likely be notifying victims through standard channels. Second, W3LL is a symptom, not the disease. These phishing kit marketplaces proliferate. Taking one down is meaningful, but the capability is now well understood by criminal actors and will be replicated.

Jordan: The MFA bypass piece is the key technical takeaway. A lot of boards feel comfortable when they hear their organization has MFA deployed. What they need to understand is that SMS and push-based MFA are now routinely defeated by adversary-in-the-middle platforms like W3LL. Phishing-resistant authentication — FIDO2, hardware keys, passkeys — is no longer aspirational. It's a gap you can quantify and defend in a budget conversation.

Alex: Now, Adobe. CVE-2026-34621. Emergency out-of-band patch for Acrobat and Reader, actively exploited since at least December 2025. It's on CISA's KEV list. This has been burning for four months before Adobe shipped a fix. The attack vector is a malicious PDF — which means any employee opening an email attachment is a potential entry point.

Jordan: Patch it today. Not this sprint, not this week's change window. Today. Adobe Acrobat and Reader exist on virtually every enterprise endpoint. This is as close to universal exposure as it gets, and the fact that active exploitation predates the patch by four months means threat actors have had a meaningful head start. Check your EDR telemetry going back to December for anything touching Acrobat processes abnormally.

Alex: And right alongside it, CISA added six vulnerabilities to the KEV catalog this week, including CVE-2026-21643 — a CVSS 9.1 SQL injection in Fortinet FortiClient EMS. Unauthenticated attacker, remote exploitation, confirmed active exploitation in the wild. If you're running FortiClient EMS, that goes into the same emergency patch bucket as the Adobe zero-day. No exceptions.

Jordan: Fortinet vulnerabilities have been a persistent theme over the past eighteen months. At this point, if you're running Fortinet infrastructure and you don't have a near-real-time patching process for their products specifically, that's a structural gap that needs a structural fix.

Alex: Let's talk supply chain, because we have two stories that belong together. Anodot, a cloud analytics platform, was breached, and the blast radius hit over a dozen enterprise customers. ShinyHunters — the same group behind several high-profile breaches — is now extorting those companies. Rockstar Games is the named victim getting the most coverage, but the more important question for every CISO listening is: what does your cloud analytics vendor have access to, and what's your contractual and technical ability to limit that access?

Jordan: SaaS analytics vendors are a category that routinely gets under-examined in third-party risk programs. They sit on top of your data lakes, your telemetry, your business metrics. The data access is broad by design — that's the product. Anodot is a wake-up call that the aggregator sitting above your data is itself a target. And separately, the Booking.com breach this week — customer reservation data, names, emails, phone numbers — is a reminder that travel and expense platforms used by your employees are also attack surface. The social engineering follow-on from that kind of data is predictable and dangerous.

Alex: Now the forward-looking piece, and this is where we want to spend a few minutes because it connects several threads we've been watching. The Cloud Security Alliance issued a formal warning this week about what they're calling an AI vulnerability storm, specifically triggered by the capabilities introduced with Anthropic's Claude Mythos. The argument is that AI models are now capable of discovering exploitable vulnerabilities at a speed that exceeds any organization's ability to remediate them. CSA is recommending CISOs invest in patch orchestration, virtual patching, and behavior-based controls as compensating measures.

Jordan: I take this seriously, and here's why. The academic research on AI-assisted vulnerability discovery has been accelerating sharply. We're past the point of theoretical. The practical implication is that the window between vulnerability existence and active exploitation is going to compress significantly. The CVD process, your patch cycles, your risk acceptance timelines — all of those were calibrated for a world where finding and weaponizing a vulnerability took human time. That assumption is breaking.

Alex: And the GitGuardian data released this week puts a number on a related problem. 28.6 million secrets exposed in public GitHub commits in 2025. Up 34 percent year over year. The single largest annual increase ever recorded. And the driver is AI agent credentials. As organizations spin up agentic workflows — AI systems authenticating to LLMs, to databases, to SaaS APIs, to cloud resources — those credentials are being hardcoded, committed to repos, and leaked at scale. Your secrets management governance almost certainly wasn't designed for this. It needs to be retrofitted explicitly for AI service accounts before the AI agent sprawl in your environment gets ahead of you.

Jordan: This is the week's theme, if you're looking for one. The attack surface is expanding faster than the governance frameworks we built to manage it. Cloud credentials, AI agent identities, SaaS dependencies, third-party data access — these are all converging. The organizations that get ahead of this are the ones that stop treating each of these as isolated problems and start treating identity and access governance as a unified, continuous program.

Alex: What we're watching the rest of this week: whether the APT41 indicators get broader sharing through ISACs, any attribution clarity on the Anodot breach, and whether CISA issues additional guidance on the Fortinet SQL injection given the criticality score.

Jordan: And whether any more W3LL victim notifications surface. If you haven't checked with your threat intel contacts on that, now is the time.

Alex: That's Cleartext for Tuesday, April 14th. 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-04-14.

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.