Cleartext

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 10 stories across 6 topic areas, including: Russian national charged in connection with Void Blizzard espionage campaign; DOJ, FBI Seize 13 Domains in Chinese Recruitment Op; Authorities dismantle crypto laundering service that moved €336 million for cybercriminals.

CyberScoop · Jun 11 · Relevance: █████████░ 9/10

Why it matters to CISOs: The DOJ indictment of a Void Blizzard operator — a Kremlin-linked group that breached at least 11 U.S. companies — provides CISOs with attribution details and TTPs useful for threat modeling against Russian state-sponsored espionage targeting enterprise networks. The arrest from Thailand signals continued U.S. law enforcement reach.

📖 Read full article

BankInfoSecurity · Jun 12 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Chinese intelligence operatives used fake recruiting firms and job offers to target current and former U.S. government employees and clearance holders — a tactic directly relevant to enterprise CISOs whose cleared personnel, contractors, and former employees are high-value social engineering targets. This underscores the need for insider threat programs that account for foreign intelligence elicitation.

📖 Read full article

Help Net Security · Jun 12 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The dismantling of AudiA6, which laundered €336M in ransomware proceeds since 2022, disrupts a key financial infrastructure layer enabling ransomware operations — providing CISOs with context on law enforcement's increasing focus on severing ransomware payment flows, which may temporarily elevate attacker desperation and retaliatory targeting.

📖 Read full article

BleepingComputer · Jun 12 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The breach of France's sovereign encrypted messaging platform exposes 73,000+ public sector employees and raises critical questions about whether government-built secure communications tools can withstand nation-state-level adversaries — directly relevant to enterprise CISOs evaluating sovereign or self-hosted messaging alternatives to commercial platforms.

📖 Read full article

BleepingComputer · Jun 12 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A breach of clinical trial patient data at the world's largest insulin producer highlights the high-value intellectual property and sensitive health data exposure facing life sciences CISOs, with regulatory and reputational consequences spanning HIPAA-equivalent frameworks across multiple jurisdictions.

📖 Read full article

BleepingComputer · Jun 11 · Relevance: █████████░ 9/10

Why it matters to CISOs: South Korea's record $409M fine against Coupang for a breach affecting 37 million customers sets a new global benchmark for regulatory enforcement consequences, directly relevant to CISOs assessing data protection liability exposure in Asia-Pacific markets and arguing for security investment at the board level. This fine rivals GDPR's largest penalties.

📖 Read full article

BleepingComputer · Jun 11 · Relevance: ████████░░ 8/10

Why it matters to CISOs: BOD 26-04 represents a structural tightening of federal patching requirements driven by AI-accelerated exploitation timelines, and enterprise CISOs should anticipate this 3-day remediation standard influencing sector-specific regulators, cyber insurance requirements, and contractual SLAs with government customers.

📖 Read full article

BankInfoSecurity · Jun 12 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Lightspeed's $37M bet on A Security — founded by a former Sygnia executive — signals investor conviction that AI-automated exploitation of agentic systems represents a sufficiently distinct threat category to warrant a new defensive category, giving CISOs a vendor to evaluate as they build defenses for autonomous AI attack surfaces.

📖 Read full article

BleepingComputer · Jun 11 · Relevance: ██████████ 10/10

Why it matters to CISOs: A critical unauthenticated RCE zero-day in Oracle PeopleSoft was actively exploited by ShinyHunters across 100+ organizations before a patch existed, making this an emergency for any enterprise running PeopleSoft HR, finance, or ERP systems. Mandiant attributes the campaign to UNC6240 with confirmed data exfiltration and extortion demands.

📖 Read full article

BleepingComputer · Jun 12 · Relevance: █████████░ 9/10

Why it matters to CISOs: A max-severity Ivanti Sentry flaw was exploited within 24 hours of disclosure, and CISA's new BOD 26-04 now mandates federal agencies patch critical exploited flaws within 3 days — a precedent that will drive pressure on enterprise security teams to compress their own remediation SLAs. Ivanti's recurring vulnerability cadence makes this a strategic vendor-risk question.

📖 Read full article

Alex: Good morning. It's Friday, June 12th, 2026. This is Cleartext. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: We've got a packed Friday show. A PeopleSoft zero-day that ShinyHunters exploited across a hundred-plus organizations before Oracle even had a patch. A record-shattering four-hundred-nine-million-dollar fine out of South Korea. Two major geopolitical operations — one Russian, one Chinese — with direct implications for your threat model and your insider threat program. CISA's new three-day patching mandate that's going to ripple well beyond the federal space. France's sovereign messaging platform gets breached. Novo Nordisk loses clinical trial data. A ransomware money laundering network goes down. And a new startup betting thirty-seven million dollars that weaponized AI needs its own defensive category. Let's get into it.

Jordan: So let's start where the pain is most immediate. If you run Oracle PeopleSoft anywhere in your environment — HR, finance, ERP — stop what you're doing and read the advisory. CVE-2026-35273 is an unauthenticated remote code execution zero-day. No credentials needed. ShinyHunters, tracked by Mandiant as UNC6240, exploited this from May 27th through June 9th. That's nearly two weeks of active exploitation before Oracle published guidance on June 10th. Mandiant has already notified more than a hundred organizations with potentially exposed servers. There are confirmed data exfiltration and extortion demands.

Alex: And the timing here is brutal. This wasn't a case where a patch dropped and people were slow to apply it. There was no patch. Your PeopleSoft instances were vulnerable and actively targeted, and the only question is whether you were in the blast radius. If you haven't already, validate your PeopleSoft exposure today. Check for indicators of compromise against the Mandiant advisory. And if you're running internet-facing PeopleSoft — which frankly, too many organizations still are — that's a conversation you need to escalate immediately.

Jordan: And while we're on the patching emergency theme, CISA slapped a three-day deadline on federal agencies to patch an actively exploited Ivanti Sentry vulnerability. Max severity. Exploited within twenty-four hours of public disclosure, which strongly suggests pre-positioned reconnaissance by the attackers. This is the first real test case for Binding Operational Directive 26-04.

Alex: Right, and BOD 26-04 is worth understanding on its own terms even if you're not a federal agency. CISA explicitly motivated this directive by citing AI-accelerated exploitation timelines. The old fourteen and twenty-one day windows are now considered dangerously slow. The new standard for critical actively exploited flaws is three days. And here's what matters for the private sector: this standard will propagate. Expect it in sector-specific regulatory guidance. Expect it in cyber insurance questionnaires. If you're a government contractor, expect it in your SLAs. Three days is the new benchmark. If your vulnerability management program can't hit that for critical exploited flaws, you have a gap that needs executive attention and probably budget.

Jordan: And the Ivanti angle specifically — this is not the first time, not the second time. Ivanti's recurring vulnerability cadence makes this a strategic vendor-risk question, not just a tactical patching question. If you're an Ivanti shop, your board should understand the risk posture that comes with that dependency.

Alex: Let's shift to the geopolitical stories, because we've got two significant ones today. Jordan, the Void Blizzard indictment.

Jordan: Denis Obrezko, thirty-six years old, Russian national, charged by DOJ for orchestrating cyberattacks attributed to Void Blizzard. This is a Kremlin-linked espionage group that compromised at least eleven U.S. companies. Obrezko was arrested in Thailand back in November 2025 and has been transferred to U.S. custody. Two things matter here for CISOs. First, the TTPs associated with Void Blizzard are now well-documented through this indictment. Use them. Update your threat models. This group has a broad enterprise targeting profile — it's not just defense and government. Second, the arrest in Thailand signals that U.S. law enforcement reach continues to extend. That's a deterrent signal, but it's a slow-acting one. Russian state-sponsored espionage targeting enterprise networks is not going to diminish because of one arrest.

Alex: And the second geopolitical story is arguably more unsettling for a different reason. DOJ and FBI seized thirteen domains tied to an alleged Chinese intelligence gathering operation. But here's the thing — this wasn't a technical intrusion. This was human targeting. Fake recruiting firms. Deceptive job offers. Aimed at current and former U.S. government employees and security clearance holders.

Jordan: This is classic intelligence tradecraft adapted for the digital age, and it should make every CISO with cleared personnel or former government employees on staff deeply uncomfortable. Your insider threat program needs to account for foreign intelligence elicitation. This isn't about someone hacking your network. It's about someone approaching your people through a LinkedIn message or a plausible job offer on a professional-looking website and extracting information through conversation. Your cleared employees, your contractors, your recently departed staff who still know your architecture — they're all targets. If your security awareness training doesn't cover this scenario specifically, it has a blind spot.

Alex: Let's move to the enforcement story that I think will dominate boardroom conversations for the next quarter. South Korea's Personal Information Protection Commission fined Coupang six-hundred-twenty-four-point-six billion won — that's roughly four hundred nine million dollars — for a breach affecting thirty-seven million customers. This is the largest data protection fine in Korean history.

Jordan: To put that in context, that rivals the biggest GDPR penalties we've seen in Europe. This is not a rounding error. This is a signal from Asia-Pacific regulators that enforcement is reaching parity with European standards.

Alex: And that's exactly the framing CISOs need to bring to their boards. If your organization operates in APAC markets, your data protection liability exposure just got repriced. South Korea, Japan, Singapore, Australia — we're seeing a convergence of enforcement posture globally. The days of treating APAC data protection regimes as softer than GDPR are over. If you need a single data point to justify increased investment in data protection controls for your APAC operations, this is it. Four hundred nine million dollars. Put that on the slide.

Jordan: Now let's talk about the Tchap breach in France. Over seventy-three thousand French public sector employee accounts compromised on France's own sovereign encrypted messaging platform. This is the tool France built specifically to avoid dependence on commercial platforms like Signal or WhatsApp for government communications.

Alex: And this is directly relevant to any enterprise CISO who's been evaluating sovereign or self-hosted messaging alternatives. The security promise of sovereign infrastructure is only as good as the engineering and operational security behind it. Building your own doesn't automatically mean building it better. If France, with significant state resources, couldn't keep Tchap secure, that should inform your risk calculus when evaluating whether to build, self-host, or rely on commercial platforms that have been battle-tested by the global threat landscape at scale.

Jordan: Speaking of breaches, Novo Nordisk — the world's largest insulin producer — disclosed a breach of clinical trial patient data. Clinical trials data is uniquely sensitive. You've got patient privacy obligations across multiple jurisdictions, competitive intellectual property value, and the regulatory burden that comes with both. The pharmaceutical sector has been under sustained targeting by both state actors and criminal groups, and this is exactly the kind of data that sits at the intersection of both motivations.

Alex: For life sciences CISOs, this is a reminder that your clinical data environments need the same defensive rigor as your crown jewel IP. And for everyone else, it's a reminder that regulatory and reputational consequences compound when the data involved is health-related. The jurisdictional complexity alone can be crippling.

Jordan: Alright, let's hit the ransomware financial infrastructure story. FBI, Europol, and international partners dismantled AudiA6, a dark web crypto laundering service that processed over three hundred thirty-six million euros — roughly three hundred eighty-nine million dollars — in illicit funds between 2022 and 2025. Multiple ransomware groups used this as a primary financial pipeline.

Alex: This is one of the largest ransomware financial infrastructure takedowns we've seen. And the strategic logic here matters. Law enforcement is increasingly focused on severing the money flows rather than just playing whack-a-mole with threat actors. If you make it harder to monetize ransomware, you change the economics of the whole operation.

Jordan: Agreed, but there's a near-term risk I want to flag. When you disrupt a major cash-out channel, you can create desperation among threat actors who have victims in the pipeline but suddenly can't monetize. That can lead to more aggressive extortion tactics, retaliatory targeting, or a temporary surge in activity as groups scramble to find alternative laundering channels. So maintain your readiness posture.

Alex: Quick hit on the funding story. A Security, founded by former Sygnia executive Yossi Torati, emerged from stealth with thirty-seven million from Lightspeed Venture Partners. Their thesis is that AI-automated exploitation of agentic systems is a sufficiently distinct threat category to require purpose-built defensive tooling.

Jordan: Interesting bet. The agentic AI attack surface is real and growing. Whether this specific company delivers or not, the market is telling you something. VCs are putting real money behind the idea that your existing security stack won't be sufficient against AI-driven autonomous exploitation. Worth tracking as you plan your architecture for autonomous systems.

Alex: Alright, outlook. Jordan, what's the thread you're pulling on as we head into next week?

Jordan: Compression. Everything is compressing. Exploitation timelines are compressing — twenty-four hours from disclosure to exploitation on Ivanti, two weeks of zero-day exploitation on PeopleSoft before anyone had a fix. Regulatory response times are compressing — CISA is now demanding three days. And the financial consequences are compressing into larger, more immediate penalties. Four hundred nine million dollars in Korea. The environment is demanding faster detection, faster response, faster patching, and the penalties for falling behind are getting steeper on every axis simultaneously.

Alex: I'd add that the human layer is getting more attention, not less. The Chinese recruitment operation isn't a technical story. It's a people story. And as we invest more in AI-driven defenses and automated patching and all the technology solutions, don't lose sight of the fact that your adversaries are still very much interested in your people. Your insider threat program, your security culture, your offboarding processes — those are every bit as critical as your patching SLA.

Jordan: Well said.

Alex: That's our show for Friday. Thanks for spending part of your morning with us. Show notes and links to every story we covered today are at cleartext.fm. Have a good weekend. Stay sharp.

Jordan: See you Monday.

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

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: North Koreans behind nearly half of US tech industry hacks, says CrowdStrike; China-linked JDY botnet expands targeting of U.S. military networks; Extortion-Only Attacks Increase, With Data Theft Dominating Ransomware Claims.

TechCrunch Security · Jun 10 · Relevance: █████████░ 9/10

Why it matters to CISOs: CrowdStrike's finding that North Korean actors account for nearly half of all U.S. tech sector intrusions in the past 12 months — primarily via fake IT workers and recruiters — demands that CISOs in tech and adjacent industries re-evaluate insider threat programs, contractor vetting, and identity controls. This is no longer a peripheral risk for high-tech firms.

📖 Read full article

BleepingComputer · Jun 10 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The JDY botnet — linked to Volt Typhoon-adjacent Chinese state actors — has expanded beyond its prior scope to actively target U.S. military networks, signaling escalating pre-positioning by China against critical defense and defense-adjacent infrastructure. Enterprises with DoD contracts or defense sector supply chain exposure face elevated reconnaissance risk.

📖 Read full article

Infosecurity Magazine · Jun 11 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The shift toward extortion-only attacks — where adversaries steal data without deploying ransomware — fundamentally undermines backup-centric resilience strategies, requiring CISOs to re-examine data classification, DLP controls, and cyber insurance coverage. The finding that most organizations cannot prevent stolen data from being exposed after an incident should directly inform incident response planning and board risk briefings.

📖 Read full article

Krebs on Security · Jun 10 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The Gentlemen has rapidly become the second most active ransomware group by victim count, using a 90% affiliate revenue split to recruit sophisticated operators — CISOs should brief incident response retainers and threat intelligence teams on this emerging group's TTPs and accelerating activity. Krebs's attribution reporting provides actionable intelligence on operator identity.

📖 Read full article

TechCrunch Security · Jun 10 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: ServiceNow is a ubiquitous enterprise platform handling sensitive HR, IT, and operational workflow data — a bug exposing customer data to the internet requires immediate verification of whether your organization's instance was among those affected, and a review of your SaaS vendor security assessment processes. This also reinforces the risk surface of deeply integrated enterprise SaaS.

📖 Read full article

BleepingComputer · Jun 11 · Relevance: █████████░ 9/10

Why it matters to CISOs: South Korea's record-breaking $409M fine for a breach affecting 37 million customers signals a global tightening of enforcement that directly informs how CISOs should frame breach risk in board-level conversations and budget requests. This benchmark will influence regulators across Asia-Pacific and beyond.

📖 Read full article

Wired Security · Jun 10 · Relevance: ████████░░ 8/10

Why it matters to CISOs: CISA's new Binding Operational Directive (BOD 26-04) compressing patch timelines to as little as 3 days for critical exploited vulnerabilities is a direct signal to enterprise security leaders that AI-accelerated exploitation is now reshaping compliance frameworks — enterprises should benchmark their own patch SLAs against this new federal standard. Board and audit committees will increasingly reference this as a reasonable standard of care.

📖 Read full article

Help Net Security · Jun 11 · Relevance: ██████████ 10/10

Why it matters to CISOs: A zero-day RCE vulnerability in Oracle PeopleSoft requiring no authentication is being actively exploited at scale across 100+ organizations — any enterprise running PeopleSoft HCM or ERP must treat this as an emergency patch priority. The ShinyHunters gang is actively harvesting data, compounding breach and regulatory exposure.

📖 Read full article

BleepingComputer · Jun 11 · Relevance: █████████░ 9/10

Why it matters to CISOs: A maximum-severity flaw in Ivanti Sentry — a widely deployed enterprise mobile gateway — is now being actively exploited to achieve root-level RCE on internet-exposed appliances, requiring immediate remediation for any organization using this product. Given Ivanti's history of rapid exploitation chains, this demands urgent attention from security teams.

📖 Read full article

Jordan: Half of all cyberattacks hitting the U.S. tech sector in the past year came from one country. Not China. Not Russia. North Korea. CrowdStrike just put a number on something a lot of us have felt for a while, and it's a number that should change how every tech CISO thinks about insider threat. That's where we start today.

Alex: Good morning. It's Thursday, June 11th, and this is Cleartext. I'm Alex Chen, alongside Jordan Reeves. We've got a packed show. We're going to dig into that CrowdStrike data on North Korean operations, then pivot to China's expanding botnet targeting U.S. military networks. We'll cover a record-breaking four-hundred-nine-million-dollar breach fine in South Korea that should be on every board's radar. CISA just compressed federal patch timelines to three days, and we need to talk about what that means for the private sector standard of care. We have two critical actively-exploited vulnerabilities — Oracle PeopleSoft and Ivanti Sentry — that demand immediate action. Plus the evolution of extortion-only attacks, a fast-rising ransomware group, and a ServiceNow exposure you need to check. Let's get into it.

Jordan: So the CrowdStrike data. Nearly fifty percent of all intrusions against U.S. tech companies in the last twelve months attributed to North Korean actors. And the primary vector isn't some exotic zero-day chain. It's people. Fake IT workers getting hired as remote contractors. Fake recruiters approaching your engineers on LinkedIn. This is social engineering at an industrial scale, and it's funding a nation-state.

Alex: What makes this so challenging from a CISO perspective is that it straddles a seam in most organizations. Insider threat programs typically focus on existing employees behaving badly. HR and procurement handle contractor vetting. Recruiting handles inbound talent. North Korea has built an operation that exploits the gaps between those functions. And if you're a tech company that scaled your remote workforce aggressively over the past few years, you need to honestly assess whether your identity verification and contractor onboarding controls are robust enough to catch a well-backstopped fake persona.

Jordan: And we should be clear about what's at stake. This isn't just espionage. North Korea's GDP growth is materially linked to revenue from these operations. They're stealing intellectual property, they're stealing cryptocurrency, they're getting paid salaries as fake contractors that flow directly back to the regime. CrowdStrike has been tracking this trajectory for years, but the scale — half of all tech sector intrusions — that's a threshold that should trigger a fundamental reassessment. If you're in tech, semiconductors, AI, biotech, defense-adjacent software — this is your primary threat actor. Not a secondary one.

Alex: The actionable takeaway here: if you haven't integrated your insider threat program with your contractor vetting and your recruiting pipeline, you're leaving a door open that the most active threat actor in your sector is specifically designed to walk through.

Jordan: Staying on the geopolitical track, let's talk about the JDY botnet. Lumen researchers have documented a significant expansion. This botnet, linked to Chinese state actors in the Volt Typhoon orbit, now comprises over fifteen hundred compromised small-office and IoT devices. And the targeting has expanded explicitly to U.S. military networks.

Alex: This is the pre-positioning story we've been discussing for two years now, and it keeps escalating. JDY isn't delivering payloads. It's mapping. It's a centrally controlled, high-performance scanner that fingerprints exposed services at scale, continuously. Think of it as persistent reconnaissance infrastructure. If you're a defense contractor, if you're in the defense industrial base supply chain, the intelligence preparation of the battlefield is happening against your network right now.

Jordan: The SOHO device angle is important here. These botnets are built on commodity routers, IP cameras, NAS boxes — devices that most enterprise security teams don't manage directly but that sit on the edges of their extended networks. Your employees' home routers. Your small-office branch equipment. This is the attack surface China keeps exploiting because it's the one nobody patches.

Alex: Let's shift to governance, because we have two stories that together paint a very clear picture of where regulatory pressure is heading. South Korea just fined Coupang six hundred twenty-four billion won — roughly four hundred nine million dollars — for a breach affecting thirty-seven million customers. That's a record for the Asia-Pacific region by an enormous margin.

Jordan: To put that in context, the previous largest South Korean enforcement action was a fraction of this. This isn't incremental escalation. This is a step function. And for any CISO operating in Asia-Pacific or with customers in the region, this number will get cited in every regulatory risk conversation for the next five years.

Alex: Exactly right. And when I talk to boards, the question is always: what's our realistic financial exposure from a breach? This gives you a very concrete data point. Regulators globally are watching each other. The EU set the pace with GDPR fines. South Korea just sent a signal that Asia-Pacific will match or exceed that aggressiveness. If your board hasn't updated its breach liability modeling recently, this is the catalyst.

Jordan: And then pair that with CISA's new Binding Operational Directive, BOD 26-04. Federal agencies now have to patch the highest-risk exploited vulnerabilities within three days. Three days. And CISA explicitly cited AI-accelerated exploitation as the driver.

Alex: This is the one I want every CISO listening to internalize, not because it applies directly to you if you're in the private sector, but because it will become the benchmark. When a plaintiff's attorney or a regulator asks what a reasonable standard of care looks like for patching critical exploited vulnerabilities, they're going to point to this directive. Three days. If the federal government says three days is the standard, your thirty-day SLA for critical vulnerabilities is going to look indefensible in litigation. The risk-tiered model CISA introduced — weighting severity, exploitability, and asset exposure — is actually well-designed. I'd encourage teams to benchmark against it voluntarily.

Jordan: Which brings us directly to two vulnerabilities that are testing everyone's patch SLAs right now. Let's start with the more severe one. CVE-2026-35273 in Oracle PeopleSoft PeopleTools, versions 8.61 and 8.62. This is a zero-day. Remote code execution. No authentication required. Oracle pushed an out-of-band alert, and Mandiant's Charles Carmakal confirmed active exploitation in the wild. ShinyHunters is already claiming data theft from over a hundred organizations through this vector.

Alex: If you run PeopleSoft HCM or ERP, stop what you're doing and patch. I don't say that lightly. An unauthenticated RCE in a system that typically holds your entire HR dataset — social security numbers, compensation data, banking information — with a financially motivated group actively harvesting that data at scale. This is an emergency. Full stop.

Jordan: Second one. Ivanti Sentry. Maximum severity. Remote code execution with root privileges on internet-exposed secure mobile gateways. Ivanti has released a patch, but active exploitation is confirmed.

Alex: Ivanti has been a recurring theme for the past three years. If you have Ivanti infrastructure exposed to the internet, you already know the drill. Patch immediately, and then conduct a compromise assessment assuming the patch window may have already been exploited. Given Ivanti's history, I'd also push your team to review whether you still need this product exposed to the internet at all, or whether there's an architectural mitigation that reduces the surface.

Jordan: Shifting to the extortion landscape. New research confirms what we've been seeing anecdotally — extortion-only attacks, where adversaries steal data without ever deploying ransomware, are increasing as a share of total incidents. Data theft now dominates ransomware insurance claims.

Alex: This is a strategic shift that should change how CISOs think about resilience. For years, the playbook was: if we have good backups, we can recover from ransomware without paying. That's still true for encryption-based attacks. But if the adversary skips encryption entirely, steals your data, and threatens to publish it, your backups are irrelevant. Your recovery plan doesn't address the actual harm. This demands investment in data classification, data loss prevention, and egress monitoring — the controls that detect and prevent exfiltration, not just recover from encryption.

Jordan: And the research highlights something uncomfortable: most organizations cannot prevent stolen data from being exposed once exfiltration has occurred. Payment doesn't reliably prevent publication. So the entire leverage model has shifted to pre-exfiltration detection. If you miss it before it leaves, your options narrow dramatically.

Alex: Two more items quickly. Krebs has a detailed attribution piece on The Gentlemen, now the second most active ransomware group by victim count. They're offering affiliates a ninety percent revenue split, which is well above industry norms, and it's fueling rapid growth. Make sure your threat intelligence team and your incident response retainer are briefed on their TTPs.

Jordan: And ServiceNow disclosed that a security bug exposed data from several customer instances to the public internet. Bug bounty activity preceded the disclosure, suggesting the exposure window may be longer than the formal timeline indicates. If you're a ServiceNow customer, verify whether your instance was affected. And more broadly, this is a reminder that deeply integrated enterprise SaaS platforms are a significant risk surface. Your ServiceNow instance probably touches HR data, IT asset data, incident data, change management workflows. That's high-value information if it's exposed.

Alex: Let's step back and look at the week's emerging theme. Jordan, what stands out to you?

Jordan: The convergence of speed and accountability. CISA is telling agencies three days to patch. Regulators are issuing four-hundred-million-dollar fines. Threat actors — whether North Korean social engineers or Chinese reconnaissance botnets or ransomware groups offering ninety-percent splits — they're all operating faster and at greater scale. The window between vulnerability disclosure and exploitation keeps compressing. The financial consequences of failing to keep up keep expanding. And the traditional organizational seams — between IT and HR, between the SOC and procurement, between the security team and the SaaS vendor — those are exactly where adversaries are operating.

Alex: I agree. The message to CISOs this week is that the standards you'll be held to are tightening from every direction — regulators, insurers, plaintiffs, and the adversaries themselves. If your program is built around thirty-day patch cycles, annual vendor assessments, and a backup-centric ransomware strategy, you're operating on assumptions that no longer hold. The organizations that will fare best are the ones treating speed, identity rigor, and data-centric controls as foundational, not aspirational.

Jordan: And if you take one action today: check your PeopleSoft exposure. That one can't wait.

Alex: That's our show for Thursday, June 11th. Show notes and links to every story we covered are at cleartext.fm. Thanks for listening. We'll see you tomorrow.

Jordan: Stay sharp.

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

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 weakens proposed telecoms defenses against Chinese hackers after industry pushback; IT sector faces growing threats from IP-hungry China, AI-enabled cybercriminals; Anthropic Offers Mythos Upgrade for Cyber Partners and a ‘Safe’ Version for the Rest of You.

The Record (Recorded Future) · Jun 09 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Industry lobbying successfully diluting Salt Typhoon-era telecoms security requirements sets a concerning precedent for the gap between regulatory intent and actual implementation, directly relevant to CISOs navigating telecom supply chain risk and critical infrastructure partnerships in the UK.

📖 Read full article

Cybersecurity Dive · Jun 09 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: CrowdStrike's annual threat intelligence report quantifying escalating Chinese state-sponsored IP theft against the IT sector, combined with North Korean remote IT worker infiltration schemes, gives CISOs concrete threat data to frame board-level discussions on nation-state risk and insider threat programs.

📖 Read full article

Wired Security · Jun 09 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Anthropic's decision to release a capability-restricted public AI model while offering the full unrestricted version to vetted cyber organizations sets a new industry precedent for AI dual-use governance — a model CISOs will need to evaluate both as a potential tool for their own teams and as a threat enablement risk.

📖 Read full article

The Hacker News · Jun 10 · Relevance: █████████░ 9/10

Why it matters to CISOs: ServiceNow is deeply embedded in enterprise IT and security operations workflows, meaning unauthorized access to customer instances could expose sensitive ITSM data, incident records, and operational configurations. CISOs should verify whether their instance was affected and review the June 5 security update status.

📖 Read full article

The Hacker News · Jun 09 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The compromise of 73 Microsoft open-source GitHub repositories to inject information-stealing malware directly threatens enterprise CI/CD pipelines that depend on Azure-sourced code and Microsoft-published samples. CISOs should audit any recent dependencies pulled from affected Microsoft GitHub organizations.

📖 Read full article

The Record (Recorded Future) · Jun 09 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A new binding operational directive will change how federal agencies prioritize vulnerabilities, with Acting Director Andersen signaling the same risk-tiering model will be promoted to critical infrastructure owners — directly affecting how enterprise CISOs should align their vulnerability management programs.

📖 Read full article

CyberScoop · Jun 09 · Relevance: ████████░░ 8/10

Why it matters to CISOs: CISA's shift toward risk-tiered vulnerability prioritization — moving away from treat-all-KEV-equally approach — will ripple into how enterprises operating as federal contractors or critical infrastructure must structure their own vulnerability management programs and board reporting.

📖 Read full article

CyberScoop · Jun 09 · Relevance: █████████░ 9/10

Why it matters to CISOs: The seventh actively exploited zero-day in Cisco SD-WAN this calendar year with no patch yet available represents an existential exposure for enterprises running distributed network infrastructure on this platform. CISOs should immediately assess SD-WAN deployment footprint and consider compensating controls.

📖 Read full article

TechCrunch Security · Jun 09 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A ransomware affiliate actively exploiting a Check Point VPN vulnerability across dozens of organizations — including government targets — with a 72-hour federal remediation mandate signals this is an emergency-tier threat for any enterprise running Check Point remote access solutions.

📖 Read full article

Alex: Welcome to Cleartext for Wednesday, June 10th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. So, the UK government spent months crafting telecoms security requirements specifically to address Salt Typhoon — arguably the most consequential espionage campaign against Western communications infrastructure in a decade — and then folded when the telcos said it was too expensive. That's where we are.

Alex: We have a packed show today. We're going to dig into that UK story and the broader pattern of nation-state threats against the IT sector. We'll cover Anthropic's fascinating new dual-track AI model. We've got two major exploitation stories — ServiceNow and Cisco SD-WAN — plus a ransomware gang burning through Check Point VPNs with a three-day federal deadline. And CISA is about to fundamentally reshape how the government prioritizes vulnerabilities, which will ripple directly into your programs. Let's get into it.

Jordan: Let's start with the UK. The Record is reporting that Britain has weakened the telecoms cybersecurity protections that were specifically designed in response to Salt Typhoon. These were proposed rules to harden network infrastructure against Chinese state-sponsored actors who had, let's be clear, already compromised major telecoms globally. The industry lobbied against the measures, and the government blinked.

Alex: This is the pattern that keeps me up at night. We have a threat intelligence community that does extraordinary work identifying and attributing these campaigns. We have regulators who, to their credit, actually tried to translate that intelligence into binding requirements. And then the implementation gap swallows everything. The telcos said the mandates were too costly or operationally burdensome, and the government rolled them back.

Jordan: What's particularly galling is the specificity here. This wasn't a generic cybersecurity framework. These were targeted defenses against a known, named, active threat actor with documented TTPs against this exact sector. Salt Typhoon compromised telcos in the US, in Europe, in Asia. The UK said, "We should do something about that," and then un-did it.

Alex: For CISOs listening, here's the direct implication. If you have telecoms supply chain dependencies in the UK — and many of you do — the regulatory floor just got lower. That means your third-party risk assessments for UK telco partners need to account for the fact that the government is no longer mandating the protections you might have assumed were coming. You own that gap now.

Jordan: And this connects directly to the CrowdStrike annual threat report that dropped yesterday. They're quantifying what we've been seeing: the IT sector is the primary target for Chinese state-sponsored IP theft campaigns. Not energy, not defense — IT. They want the tools that build everything else.

Alex: The report also flags AI-enabled acceleration of attacks and, notably, North Korean remote IT worker infiltration. That second one is something I think a lot of organizations still treat as an edge case. It's not. If you don't have robust identity verification in your hiring pipeline for remote technical roles, you have an insider threat problem you haven't scoped yet.

Jordan: The North Korean IT worker schemes are genuinely clever. These aren't crude attempts. They're using sophisticated identity packages, VPN infrastructure to mask their location, and they're targeting roles that give them access to source code and internal systems. If your insider threat program is still oriented around disgruntled employees, you're fighting the last war.

Alex: Let's shift to Anthropic, because this is a story that has significant strategic implications. They've released two versions of their latest model. Claude Fable 5 is the public version with safety classifiers that Anthropic says prevent use for cyberattacks. Claude Mythos 5 is the same underlying model with those restrictions removed, available only to vetted cybersecurity organizations.

Jordan: This is the first time we've seen a major AI lab formally implement a tiered-access model for offensive capabilities. Anthropic is essentially saying: this model can do things that are dangerous, so we're going to let the good guys have the full version and give everyone else the guardrailed version. They claim no universal jailbreaks exist in Fable 5's safety layer.

Alex: I have two reactions. First, as a governance precedent, this is significant and probably inevitable. We were always heading toward a world where AI capabilities would be gated by trust level. Anthropic just formalized it. Second, the "no universal jailbreaks" claim is bold. Every safety layer eventually gets circumvented. The question is how long and at what cost to the attacker.

Jordan: Right. The practical question for CISOs is twofold. Are you evaluating Mythos 5 as a tool for your red team or threat intelligence functions? Because if your adversaries have access to unrestricted models — and some of them do — your defensive teams need parity. And simultaneously, are you modeling the risk that safety classifiers on public models erode over time?

Alex: Both good questions. I'd add a third: how does this affect your AI governance policy? If you're a vetted partner getting Mythos 5, you now have a dual-use tool inside your organization that requires its own access controls and audit trail. That's a new category of asset management for most shops.

Jordan: Let's move to the active exploitation stories, because there are several and they're all urgent. ServiceNow disclosed that threat actors exploited an unauthenticated access flaw via an API endpoint to gain what they're calling "deeper unauthorized access" to customer instances. They patched hosted instances on June 5th.

Alex: ServiceNow is the nervous system of enterprise IT operations for a huge swath of our audience. Your ITSM data, your incident records, your change management workflows, your CMDB — it's all there. Unauthorized access to a ServiceNow instance isn't just a data breach. It's an intelligence goldmine for an attacker mapping your environment.

Jordan: The "unauthenticated" part is what makes this particularly concerning. No credentials required. If you're running ServiceNow, verify your instance was patched as of June 5th. If you're self-hosted, which some of you are, check the advisory immediately. And review your API endpoint exposure. This is the kind of flaw that gets found because attackers are systematically probing SaaS APIs.

Alex: Next up, the Microsoft GitHub compromise. Seventy-three repositories across Azure, Microsoft, Azure-Samples, and MicrosoftDocs organizations were compromised to inject an information stealer. Microsoft temporarily took repos offline, and the investigation — dubbed Miasma — is ongoing. Some repos are back, others aren't.

Jordan: This is a supply chain attack against one of the largest open-source publishers on the planet. If your CI/CD pipelines pull from Microsoft GitHub organizations — and statistically, many of you do — you need to audit what you've consumed recently. The injected code was an infostealer, which means credentials, tokens, and session data from developer workstations and build environments could be compromised.

Alex: The remediation here is painful but necessary. Identify any dependencies sourced from the affected organizations during the compromise window. Rebuild from known-good sources. Rotate credentials on any build systems that may have executed compromised code. This is exactly the scenario that makes software supply chain security so difficult at scale.

Jordan: Now, Cisco SD-WAN. This is the seventh — seventh — actively exploited zero-day in Cisco SD-WAN products this calendar year. And there's no patch. Active exploitation confirmed in the wild.

Alex: Seven zero-days in one product line in six months. At some point, this stops being a vulnerability management problem and becomes an architecture problem. If you're running Cisco SD-WAN, you need to be having a serious conversation about your network infrastructure strategy. Compensating controls, segmentation, monitoring — yes, all of that immediately. But also, what's your long-term plan?

Jordan: And on the Check Point side, CISA gave federal agencies a 72-hour remediation window for a VPN vulnerability that a ransomware affiliate is actively exploiting across dozens of organizations. Three days. That tells you everything about the severity.

Alex: If you're running Check Point remote access VPN, this is a drop-everything item. A ransomware affiliate at scale means this is already weaponized, already automated, and already being used against targets of opportunity. Don't wait for your normal patch cycle.

Jordan: The last story ties several threads together. CISA is releasing a binding operational directive today — Wednesday — that fundamentally changes how federal agencies prioritize vulnerabilities. Acting Director Andersen is signaling this is a move away from the treat-all-KEV-entries-equally approach toward explicit risk tiering. Some vulnerabilities get elevated, others get deprioritized.

Alex: This is long overdue and directionally correct. The KEV catalog was a breakthrough, but the flat priority model created perverse incentives. Agencies were burning cycles on lower-risk KEV entries while higher-impact vulnerabilities outside the catalog went unaddressed. Risk tiering acknowledges operational reality.

Jordan: Andersen also indicated this framework will extend into critical infrastructure and private sector guidance. So if you're a federal contractor or you operate in any of the critical infrastructure sectors, expect this to reshape your compliance conversations within months.

Alex: For CISOs, this is a chance to get ahead. If CISA is moving toward risk-tiered vulnerability prioritization, align your program now. The organizations that can demonstrate their vulnerability management already reflects business-context risk tiering will be in a much stronger position when this becomes the expected standard.

Jordan: Looking at the week's arc, there's a clear theme: the gap between knowing and doing. We know Salt Typhoon is real, but the UK can't sustain the regulatory will to address it. We know Cisco SD-WAN is fundamentally compromised, but organizations are still running it. We know AI capabilities need governance, and Anthropic is the first to actually try. The question isn't whether we have the intelligence. It's whether institutions have the will to act on it.

Alex: And that's exactly the role of the CISO right now. You are the translation layer between threat intelligence and organizational action. The UK telco story is a warning: if you delegate your security posture to regulatory mandates, you're exposed to political winds. Own your risk. Build your program to the threat, not to the compliance floor.

Jordan: Well said.

Alex: That's our show for Wednesday, June 10th. Show notes and links to every story we covered are at cleartext.fm. We'll be back tomorrow. Stay sharp.

Jordan: Stay sharp.

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

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 10 stories across 5 topic areas, including: Iran Signed a Ceasefire — Its Hackers Didn't; Microsoft’s open source tools were hacked to steal passwords of AI developers; French government messaging platform breached through account hijacking.

Dark Reading · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Iranian state-affiliated threat actors continued cyber operations despite a diplomatic ceasefire, underscoring the disconnect between geopolitical agreements and actual threat actor behavior — CISOs with exposure to Middle East-linked sectors or critical infrastructure should not reduce threat monitoring based on political developments.

📖 Read full article

TechCrunch Security · Jun 08 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Attackers compromised Microsoft's GitHub repositories for Azure and AI coding tools to harvest developer credentials, posing a direct supply-chain risk for enterprises using these tools to build or deploy AI systems.

📖 Read full article

Help Net Security · Jun 09 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The compromise of France's sovereign secure messaging platform via account hijacking illustrates that even purpose-built, state-managed communications infrastructure is vulnerable to credential-based attacks — a cautionary case for CISOs evaluating secure communications solutions and privileged account controls.

📖 Read full article

BleepingComputer · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The compromise of 19 widely downloaded PyPI packages targeting developer secrets is a significant supply-chain event, particularly for enterprises with data science, AI/ML, or research engineering teams that routinely pull open-source scientific libraries.

📖 Read full article

CyberScoop · Jun 08 · Relevance: ████████░░ 8/10

Why it matters to CISOs: NSO Group allegedly conducted new spearphishing campaigns against WhatsApp users in violation of a court injunction, signaling that commercial spyware operators remain active threats despite legal constraints — a relevant risk for executives and high-value targets inside enterprise organizations.

📖 Read full article

Cybersecurity Dive · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Insurers are tightening underwriting standards and applying more restrictions and exclusions following years of soft market pricing, directly affecting the cyber risk transfer strategies that CISOs present to boards and CFOs.

📖 Read full article

BankInfoSecurity · Jun 09 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Congressional scrutiny of a 1.8 million-person health system breach is escalating to the mayor and CEO level, signaling that legislators are increasingly willing to hold senior executives personally accountable for cyber incidents — a governance dynamic CISOs in regulated industries must factor into their program narratives.

📖 Read full article

BankInfoSecurity · Jun 09 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The 2026 RSAC Innovation Sandbox winner securing $30M Series A validates that AI agent governance and behavioral monitoring is becoming a recognized enterprise security category that CISOs will need to evaluate as autonomous AI deployments accelerate.

📖 Read full article

BleepingComputer · Jun 09 · Relevance: █████████░ 9/10

Why it matters to CISOs: A critical authentication bypass (CVSS 9.3) in Check Point Remote Access VPN is being actively exploited by Qilin ransomware affiliates since early May; any enterprise running IKEv1-configured Check Point VPN deployments faces immediate ransomware risk and must patch or mitigate urgently.

📖 Read full article

CyberScoop · Jun 09 · Relevance: █████████░ 9/10

Why it matters to CISOs: This is the seventh actively exploited zero-day in Cisco SD-WAN products this year, with no patch yet available, representing a serious and ongoing exposure for the large number of enterprises relying on Cisco SD-WAN for core network infrastructure.

📖 Read full article

Alex: Good morning. It's Tuesday, June 9th, 2026. This is Cleartext. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Let's get into it.

Alex: We've got a loaded show today. Two critical zero-days that need your attention this morning, a supply-chain compromise hitting Microsoft's own AI development tools, a pair of stories that remind us legal constraints don't stop sophisticated adversaries, insurance underwriting getting tighter, and Congress coming for healthcare executives after a major breach. Plus a quick look at a new AI security startup that just won the RSAC Innovation Sandbox.

Jordan: But we're starting where I think every CISO running Check Point VPN infrastructure needs to start their morning, which is with CVE-2026-50751. This is a CVSS 9.3 authentication bypass in Check Point Remote Access VPN. It targets certificate-based auth on IKEv1 configurations. Unauthenticated, remote, and Qilin ransomware affiliates have been exploiting it as a zero-day since at least early May. CISA added it to the KEV catalog and gave federal agencies three days to patch. Three days. That tells you the severity they're seeing in the wild.

Alex: And three days from CISA is effectively an order. For those of you outside the federal space, treat this with the same urgency. If you're running IKEv1 configurations on Check Point Remote Access VPN, you need to verify patch status this morning, or have compensating controls documented and in place by end of day. Qilin is not a theoretical threat. They're active, they're capable, and VPN appliances are the front door.

Jordan: And while we're on network infrastructure, let's talk about the other zero-day. Cisco SD-WAN. Again. This is the seventh actively exploited zero-day in Cisco SD-WAN products in 2026. Seventh. And Cisco has not released a patch yet.

Alex: Seven zero-days in one product family in six months is not a vulnerability management problem. That's a strategic risk problem. If you're a CISO running Cisco SD-WAN as your core WAN fabric, you need to be having a different conversation with your board than you were having in January. This is the kind of pattern that should trigger an architecture review, not just another patch cycle.

Jordan: Right. And when there's no patch available, you're in compensating controls territory, which means segmentation, enhanced monitoring, restricting management plane access, and frankly having a very honest conversation with your Cisco account team about their roadmap for getting this product line under control.

Alex: Let's shift to supply chain, because we have two significant stories there. First, Microsoft's own GitHub repositories for Azure and AI coding tools were compromised. Attackers used the access to steal credentials from AI developers. Microsoft shut down dozens of repositories in response.

Jordan: This one matters for a specific reason. The attack surface here isn't some obscure third-party library. This is Microsoft's own open-source tooling for Azure and AI development. If you're building on Azure AI services, your developers were likely pulling from these repos. The credential harvesting design means this could have downstream consequences we haven't seen yet, compromised developer credentials feeding into lateral movement, cloud account takeover, pipeline poisoning.

Alex: And then there's the Shai-Hulud attack. Nineteen science-focused PyPI packages trojanized, collectively downloaded hundreds of thousands of times. Same playbook, steal developer secrets, but this one targets data science and ML teams specifically.

Jordan: So if you're running an AI or ML program, and at this point most enterprises are, you had two independent supply-chain events in the same week targeting your development teams. This is the trend we've been talking about all year. The AI development toolchain is the new high-value target. Software composition analysis, dependency pinning, artifact verification. These aren't nice-to-haves anymore. They're table stakes.

Alex: Let's move to two stories that share a common thread, which is that legal and diplomatic constraints don't reliably constrain sophisticated adversaries. First, Iran. Dark Reading is reporting that Iranian state-affiliated threat actors continued active cyber operations despite Iran signing a ceasefire agreement.

Jordan: This should surprise exactly no one, but it's worth saying explicitly because I know there are organizations that factor geopolitical developments into their threat modeling, and they should. But the direction of that adjustment matters. A ceasefire does not reduce cyber risk. If anything, cyber operations become more attractive to a state actor during a ceasefire because they're deniable, they're below the threshold of kinetic response, and they maintain strategic leverage without violating the letter of the agreement. The article raises an interesting question about whether extensions of the Geneva Conventions could impose restrictions on cyberwarfare under ceasefire conditions. And that's a worthy legal debate. But it's a debate that will take years to resolve, and in the meantime, your threat model should assume that nation-state cyber operations persist through diplomatic pauses.

Alex: The same principle applies to the NSO Group story. Meta filed a federal contempt of court complaint alleging that NSO Group conducted new spearphishing campaigns against WhatsApp users in direct violation of a permanent injunction. Meta detected and blocked the campaign, but the point stands. A court order did not deter a commercial spyware operator from targeting the same platform it was ordered to leave alone.

Jordan: NSO Group is essentially saying through its behavior that the legal system moves too slowly to constrain them in real time. And for CISOs, the practical takeaway is that if you have executives, board members, or high-value personnel who are targets for commercial spyware, you cannot rely on legal deterrence as a control. You need technical controls. Device management, hardened communications, behavioral monitoring on executive endpoints.

Alex: These two stories together reinforce something I've said to boards many times. Legal and diplomatic frameworks are lagging indicators. Your security program needs to be calibrated to actual threat actor behavior, not to what's been agreed to on paper.

Jordan: Well said.

Alex: Let's talk about the French government messaging breach. Tchap, which is France's sovereign secure messaging platform built on the Matrix protocol, was compromised through a hijacked user account. Attackers gained access to public chat rooms used by government personnel. DINUM, France's interministerial digital directorate, is investigating.

Jordan: This is a cautionary tale for anyone who thinks building your own secure messaging platform solves the problem. Tchap was purpose-built to keep French government communications off commercial platforms. It's Matrix-based, self-hosted, theoretically sovereign. And it was compromised through the oldest attack vector in the book, a hijacked account. The protocol doesn't matter if the identity layer is weak. Credential-based attacks defeat architecture every time.

Alex: For CISOs evaluating secure communications solutions, the lesson is clear. The platform is only as strong as the access controls protecting it. MFA enforcement, session management, privileged account monitoring. These are the controls that determine whether your secure messaging platform is actually secure.

Jordan: Moving to governance. Senator Bill Cassidy, chair of the Senate HELP Committee, is now directly questioning the CEO of NYC Health and Hospitals and the Mayor of New York City about cyber practices following the 2025 breach that affected 1.8 million patients.

Alex: This is significant for the governance trajectory it signals. We're watching congressional inquiry reach past the CISO, past the CIO, directly to the CEO and the political leadership of a municipality. NYC Health and Hospitals is the largest municipal public health system in the country. When a breach of that scale triggers direct Senate scrutiny of the CEO and the mayor, it sends a message to every health system executive in the country. Cyber is no longer delegable.

Jordan: And if you're a CISO in healthcare or any regulated industry, this changes your internal narrative. When you're presenting to your board, you can now point to a concrete example of congressional leaders personally holding CEOs accountable for breach outcomes. That's leverage.

Alex: On insurance. Cybersecurity Dive is reporting that the multiyear soft market in cyber insurance is reversing. Underwriters are tightening standards, introducing new exclusions, and applying more scrutiny at both renewal and claims stages.

Jordan: This was inevitable. The soft pricing was unsustainable given loss ratios, and now the correction is here. For CISOs, this means two things. First, your renewal process is about to get harder. Expect more rigorous security control verification. And second, your risk transfer strategy needs a reality check. If exclusions are narrowing coverage, the residual risk sitting with the organization just got larger, and your board needs to know that.

Alex: Quick hit on the startup front. Geordie AI, winner of the 2026 RSAC Innovation Sandbox, just raised thirty million in Series A funding. They're building a platform for visibility, governance, and behavioral monitoring of AI agents across cloud, code, and endpoint environments.

Jordan: This is a category that's going to get crowded fast. But the Innovation Sandbox win and the funding signal that the market recognizes AI agent governance as a real problem. If you're deploying autonomous AI systems, this is a space to watch. Not necessarily this vendor specifically, but the category.

Alex: All right, let's look ahead. Jordan, what's the thread you're pulling on this week?

Jordan: Supply-chain attacks on AI development infrastructure. We had two independent events this week, Microsoft's repos and the PyPI compromise, both targeting developer credentials in AI toolchains. This is not coincidental. Threat actors are following the money and the strategic value, and right now that's AI development pipelines. I expect this to accelerate. CISOs need to get ahead of it by treating their AI development environments with the same rigor they apply to production systems.

Alex: I agree. And on the governance side, I'm watching the convergence of insurance tightening and congressional accountability. When your risk transfer options are narrowing and your personal liability is expanding, the calculus for security investment changes. I think we're going to see more CISOs making the case for increased program funding not on the basis of threat landscape alone, but on the basis of executive liability and insurability. That's a board-level conversation, and it's one that's getting easier to have with every story like the NYC Health inquiry.

Jordan: Good place to leave it.

Alex: That's Cleartext for Tuesday, June 9th, 2026. Show notes and links to every story we covered are at cleartext.fm. We'll be back tomorrow. Stay sharp.

Jordan: Talk then.

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

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 10 stories across 5 topic areas, including: VerdantBamboo Deploys BSD Variant of BRICKSTORM on Linux Appliances; Russia upgrades rules for its digital spy system to better track citizens online; Risky Bulletin: RubyGems adds dependency cooldowns to counter supply chain attacks.

The Hacker News · Jun 08 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A China-nexus espionage cluster (VerdantBamboo/Clay Typhoon) is actively expanding its Linux and BSD malware toolkit against enterprise network appliances, representing a persistent and evolving threat to the network edge that CISOs must account for in their threat models.

📖 Read full article

The Record (Recorded Future) · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Russia's updated SORM technical standards expand state surveillance capabilities, directly impacting multinationals with Russian operations and raising data sovereignty and employee privacy risks that legal and security teams must jointly assess.

📖 Read full article

Risky Business News · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: This bulletin bundles several high-signal items for CISOs: IBM/AT&T hidden-hack allegations, a new Cisco SD-WAN zero-day warning, Google security team layoffs, and a supply chain defense measure from RubyGems — providing efficient situational awareness across multiple risk domains.

📖 Read full article

BankInfoSecurity · Jun 08 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: As AI agents are granted autonomous access to sensitive data and systems, CISOs must extend their insider threat programs to govern non-human identities — including audit trails, least-privilege access, and behavioral baselines for AI workflows.

📖 Read full article

BankInfoSecurity · Jun 08 · Relevance: █████████░ 9/10

Why it matters to CISOs: A False Claims Act whistleblower suit alleging IBM and AT&T concealed security failures to maintain federal contracts raises serious board-level questions about vendor due diligence obligations and the legal exposure CISOs face when managing third-party security representations.

📖 Read full article

The Hacker News · Jun 08 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Google Mandiant's attribution of a multi-vector vishing-plus-physical-intrusion extortion campaign targeting professional, legal, and financial services firms signals that threat actors are now combining social engineering with physical access — demanding CISOs reassess physical security integration with their cyber programs.

📖 Read full article

TechCrunch Security · Jun 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: This mid-year breach retrospective from TechCrunch provides board-ready context on the threat landscape, covering a DOGE data breach, critical infrastructure attacks on energy and water systems, and the compromise of an FBI surveillance system — essential briefing material for CISO-to-board communications.

📖 Read full article

BleepingComputer · Jun 07 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Mandiant's detailed report on Silent Ransom Group's vishing-to-data-theft pipeline targeting law firms and professional services — achieving exfiltration within hours of first contact — should prompt CISOs to harden help desk authentication and run tabletop exercises against social engineering scenarios.

📖 Read full article

TechCrunch Security · Jun 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Massachusetts' passage of a comprehensive privacy bill with a blanket ban on selling precise location data adds another state-level compliance obligation for enterprises, accelerating the need for a unified data governance framework that can accommodate a patchwork of U.S. state privacy laws.

📖 Read full article

Help Net Security · Jun 08 · Relevance: █████████░ 9/10

Why it matters to CISOs: A critical authentication bypass (CVSS 9.3) in Check Point Remote Access VPN is being actively exploited by a Qilin ransomware affiliate — organizations running Check Point VPN in IKEv1 mode face immediate ransomware exposure and must patch or mitigate by emergency change control.

📖 Read full article

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

Jordan: And I'm Jordan Reeves. Let's get into it.

Alex: We have a packed show today. A Check Point VPN zero-day that's already being exploited by ransomware operators, a whistleblower lawsuit that should make every CISO rethink their vendor contracts, China-nexus actors expanding their toolkit on network edge devices, threat actors literally walking into buildings to steal data, and Massachusetts just added another tile to the privacy compliance mosaic. Plus, we'll touch on Russia's surveillance upgrades, RubyGems taking a stand on supply chain attacks, and why your AI agents might be your newest insider threat.

Jordan: But let's start where the fire is hottest. If you're running Check Point Remote Access VPN, stop what you're doing and go check your patching status. CVE-2026-50751. CVSS 9.3. Authentication bypass. And it's not theoretical — a Qilin ransomware affiliate is actively exploiting this in the wild as a zero-day.

Alex: Walk us through the mechanics, Jordan.

Jordan: It's an authentication bypass affecting both Check Point Remote Access VPN and Mobile Access. Specifically, if you're running IKEv1 mode, an unauthenticated remote attacker can bypass both certificate validation and password authentication. That's full bypass. No credentials needed. Check Point has released patches, so this is an emergency change control situation. If you can't patch immediately, you need compensating controls — disable IKEv1 if possible, restrict access at the network layer, and assume compromise if you've been running an exposed instance.

Alex: And the fact that Qilin is the affiliate exploiting this matters. They're one of the more aggressive ransomware-as-a-service operations right now. They're not sitting on zero-days to be patient. They move fast, they exfiltrate, and they extort. So the window between exploitation and catastrophic data loss is compressed.

Jordan: Right. And this is a pattern we keep seeing. VPN appliances at the network edge continue to be the single most consequential attack surface for enterprise defenders. Ivanti, Fortinet, Palo Alto, now Check Point again. The perimeter device is the perimeter problem.

Alex: Which is a perfect segue into our next story, because China-nexus actors are thinking exactly the same way. Volexity published research today on VerdantBamboo — that's their name for the cluster Microsoft tracks as Clay Typhoon — deploying a BSD variant of the BRICKSTORM backdoor along with two other malware families, PLENET and AGENTPSD, specifically targeting Linux appliances.

Jordan: This is significant for a couple of reasons. First, the BSD variant. When you see a threat actor invest in porting their implant to BSD, they're not doing it for academic interest. They're doing it because they've encountered BSD-based appliances in target environments and they need persistent access on those platforms. This is capability expansion driven by operational necessity.

Alex: And what does that tell us about their targeting?

Jordan: It tells us they're inside networks where enterprise-grade network appliances run BSD derivatives — think firewalls, load balancers, specialized routing infrastructure. These are the devices that sit between segments, that handle sensitive traffic, that defenders often have limited visibility into. VerdantBamboo is building a cross-platform toolkit specifically to live on the infrastructure that most organizations treat as black boxes from a detection standpoint.

Alex: So the action item for CISOs here is twofold. One, make sure your threat model explicitly accounts for compromise of network appliances, not just endpoints. Two, if you're in sectors that Chinese state-affiliated actors historically target — defense industrial base, telecom, technology, critical infrastructure — you should be working with your detection teams to hunt for indicators associated with BRICKSTORM and these related families. Volexity's report has the technical details.

Jordan: And honestly, even if you're not in those sectors, the techniques transfer. Once these toolkits mature, they get reused across campaigns.

Alex: Let's shift to what might be the most consequential story of the day from a governance and liability perspective. A former IBM vice president of threat intelligence has filed a False Claims Act lawsuit alleging that IBM and AT&T concealed significant cybersecurity deficiencies while holding major federal government contracts.

Jordan: This is the kind of story that should be circulating in every CISO's legal and compliance channels today. The allegation is that basic security controls were not implemented, that known deficiencies went unresolved for years, and that sensitive federal data was potentially exposed throughout. And the vehicle here — the False Claims Act — is designed exactly for this. It carries treble damages and it's built for cases where contractors misrepresent their performance to the government.

Alex: Let me frame why this matters beyond IBM and AT&T. If you're a CISO at any organization that relies on managed security services or outsourced IT from major vendors, this case should trigger a hard look at your vendor due diligence process. What security representations are in your contracts? How do you verify them? And critically, what's your legal exposure if a vendor you selected is later found to have misrepresented their security posture?

Jordan: And for CISOs who are themselves at service providers or contractors — especially those with government work — this is a signal that the enforcement environment is tightening. The DOJ's Civil Cyber-Fraud Initiative has been building momentum. This lawsuit, if the allegations hold, could set precedent for what constitutes adequate cybersecurity disclosure by federal contractors. That's board-level risk.

Alex: Absolutely. I'd recommend every CISO with federal contract exposure brief their general counsel on this case this week.

Jordan: Now let's talk about a threat that's literally walking through the front door. Google Mandiant and GTIG published a detailed attribution on UNC3753, also known as the Silent Ransom Group. Between January and May of this year, they targeted dozens of U.S. professional services, legal, and financial services organizations using a combined vishing and physical intrusion playbook.

Alex: Break down that attack chain.

Jordan: It starts with voice phishing — fake IT support calls. They're convincing enough to get initial access or credentials. But what makes this campaign distinctive is the physical component. They're conducting actual physical intrusions into target facilities to support data theft. And the timeline is compressed — Mandiant reports data exfiltration within hours of initial contact. They're not deploying ransomware. They're stealing data and going straight to extortion.

Alex: This is a wake-up call for how siloed most organizations still are between physical security and cybersecurity. Your SOC might be world-class, but if someone can social engineer their way past the front desk and plug into your network from a conference room, none of that matters.

Jordan: Law firms are particularly vulnerable here because of the nature of the data they hold — privileged communications, M&A details, litigation strategy. The extortion leverage is enormous. But this pattern will expand to other sectors. If you're a CISO, run a tabletop exercise this quarter that explicitly includes a combined social engineering and physical access scenario. And harden your help desk authentication immediately. If your IT support team can't verify caller identity through a secure channel, you have a gap that this group will exploit.

Alex: The BleepingComputer coverage adds useful operational detail on the law firm targeting specifically. Check our show notes for both sources.

Jordan: Let's move to Russia. The Ministry of Digital Development published updated technical standards for SORM — the System for Operative Investigative Activities — at the end of May. This is Russia's state-mandated surveillance infrastructure that all telecom and internet providers operating in Russia must support.

Alex: For CISOs at multinationals with Russian operations, employees, or data flows touching Russia, this is a compliance and risk story. The upgraded SORM standards expand the state's technical interception capabilities. That means any data transiting Russian infrastructure — email, messaging, browsing, VPN traffic — faces an elevated interception risk under a legal framework that offers essentially zero transparency or recourse.

Jordan: And the practical implication is that your legal team and your security team need to jointly assess what data exposure exists in Russian operations. If you haven't already segmented Russian operations from your core enterprise infrastructure, this should accelerate that conversation.

Alex: Staying on governance, Massachusetts passed a comprehensive privacy bill that includes a blanket ban on selling precise location data. This makes Massachusetts the latest state to join what is now a thoroughly fragmented U.S. privacy landscape.

Jordan: The location data ban is the sharp edge here. If your organization uses, brokers, or passes location data through marketing, HR analytics, fleet management, anything — you now have another state-specific prohibition to comply with. And the patchwork keeps growing.

Alex: If you don't have a unified data governance framework that can accommodate state-by-state variation, you're building compliance debt that will compound. This is an area where investment now saves you emergency spend later.

Jordan: Two more items, quickly. RubyGems is implementing dependency cooldowns — essentially a waiting period before new dependencies can be consumed — as a defense against supply chain attacks. It's a simple, elegant control. It won't stop everything, but it raises the cost for attackers who rely on typosquatting and dependency confusion. Other package managers should follow suit.

Alex: And from the same Risky Business bulletin, Cisco has warned of a new SD-WAN zero-day, and Google layoffs have reportedly hit security teams. That second item is worth watching. When a platform provider that handles a significant portion of the internet's infrastructure reduces its security headcount, that's a systemic risk signal that deserves attention.

Jordan: Last segment before our outlook. BankInfoSecurity published a thoughtful piece on AI agents as the new insider threat. As AI agents are granted autonomous access to systems and data — executing multi-step workflows with minimal human oversight — they functionally mirror insider risk profiles.

Alex: This is the governance challenge I keep raising with boards. Your insider threat program was designed for humans. It assumes behavioral patterns, access request workflows, and audit trails that are built around human decision-making. AI agents don't fit that model. They access data at machine speed, across systems, and often with overly broad permissions because the use case demanded it.

Jordan: The fix isn't exotic. It's applying the same principles — least privilege, behavioral baselines, audit trails — but extending them to non-human identities. If your IAM program doesn't have a workstream for AI agent governance, you're behind.

Alex: Looking at the week ahead, Jordan, what's the through-line you see?

Jordan: The theme is convergence of threat vectors. Physical and cyber in the UNC3753 campaign. Network appliances becoming the primary target for both Chinese espionage and ransomware affiliates. AI agents creating insider risk at machine scale. The boundaries that we've used to organize security programs — physical versus cyber, human versus non-human, endpoint versus network — those boundaries are becoming liabilities. The threat actors don't respect them, and our organizational structures shouldn't either.

Alex: I'd add the governance dimension. Between the IBM-AT&T whistleblower case, Massachusetts privacy law, and Russia's SORM upgrades, CISOs are operating in an environment where the legal and regulatory consequences of security decisions are accelerating faster than the threat landscape itself. If your board isn't hearing about legal exposure alongside technical risk, you're telling an incomplete story.

Jordan: Well said. Busy week ahead.

Alex: That's Cleartext for Monday, June 8th, 2026. Show notes and links to every story we covered are at cleartext.fm. We'll see you tomorrow.

Jordan: Stay sharp.

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

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: Anthropic scales Claude Mythos to critical infrastructure in 15+ countries; NSA said to be readying Anthropic’s Mythos for use in cyber operations; Chinese APT deploys new malware to keep access to hacked networks.

TechCrunch Security · Jun 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: Anthropic deploying its most capable and restricted AI model — Mythos — to power, water, healthcare, and communications operators across 15 countries marks a strategic inflection point where frontier AI becomes a critical infrastructure dependency, creating novel supply chain and model-integrity risks CISOs must now plan for.

📖 Read full article

TechCrunch Security · Jun 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The NSA's reported preparation of Claude Mythos for offensive cyber operations — despite a federal ban on using the model maker — signals that AI-enabled offensive capabilities are now operational-level considerations for nation-states, raising the threat bar for any organization that is a potential nation-state target.

📖 Read full article

BleepingComputer · Jun 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: UNC5221's deployment of two previously undocumented malware families (Plenet and AgentPSD) alongside the Brickstorm backdoor in Microsoft 365 environments signals a Chinese espionage capability upgrade specifically targeting enterprise cloud tenants — M365 audit log review and conditional access policy hardening are now urgent.

📖 Read full article

Risky Business News · Jun 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The US military's confirmed use of commercial location data to target personnel in the Iran conflict (Operation Epic Fury) is a direct warning to enterprise CISOs: commercial data brokers are selling information that nation-states — including China — are analyzing in peacetime for intelligence and counter-espionage purposes against corporate targets.

📖 Read full article

Krebs on Security · Jun 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: This is the week's defining AI security failure: a production AI agent designed to help users became the attack vector itself, requiring no malware, no credential theft, and no prompt injection — the agent simply did what it was built to do. CISOs must audit every AI-powered support and workflow agent for account-action authority before deployment.

📖 Read full article

The Hacker News · Jun 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: A self-replicating supply chain worm compromising Microsoft's own Azure, Azure-Samples, Microsoft, and MicrosoftDocs GitHub organizations is an enterprise-level trust crisis — any code pulled from those repositories during the infection window must be treated as potentially tainted.

📖 Read full article

The Hacker News · Jun 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Self-spreading worms in the npm ecosystem that hide behind eBPF kernel rootkits represent a severe threat to developer pipelines; security teams should treat any npm package touched in the last week with elevated scrutiny and validate SBOM integrity.

📖 Read full article

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

Why it matters to CISOs: A False Claims Act lawsuit alleging IBM and AT&T concealed breaches and security control failures while holding major federal government contracts is a landmark accountability moment — CISOs at government contractors must audit their own breach disclosure practices against FCA exposure risk.

📖 Read full article

The Hacker News · Jun 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A five-month undetected exfiltration of a senior financial executive's Outlook inbox — routed through Dropbox and OneDrive to blend with normal cloud traffic — is a blueprint for long-dwell espionage that most DLP and SIEM configurations will miss; CISOs in financial services must review cloud exfiltration detection coverage.

📖 Read full article

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

Why it matters to CISOs: A successful brute-force bypass of Dashlane's 2FA protecting encrypted password vaults is a direct threat to enterprise credential hygiene — CISOs should assess whether enterprise Dashlane deployments use the affected personal subscription tier and verify that master password strength policies are enforced.

📖 Read full article

CyberScoop · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The White House's voluntary-framework AI EO, combined with a sprawling House AI bill proposing to preempt all state AI laws, sets the regulatory context CISOs must navigate when building AI governance programs — voluntary federal standards now appear to be the ceiling, not the floor, for the foreseeable future.

📖 Read full article

CyberScoop · Jun 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A proposed $250M CISA budget cut in the FY2027 DHS appropriations bill, combined with the agency's concurrent assignment of new AI security responsibilities, creates a structural capability gap that enterprise CISOs relying on CISA advisories, KEV catalog updates, and threat sharing must now account for in their own programs.

📖 Read full article

Cybersecurity Dive · Jun 03 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: CISA and FBI's joint advisory on attacks against internet-exposed automatic tank gauge systems — used across energy, agriculture, and transportation — is a direct call to action for CISOs with OT/ICS environments to audit internet-facing industrial monitoring devices for exposure and authentication controls.

📖 Read full article

VentureBeat Security · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Microsoft Execution Containers (MXC) — a policy-driven, OS-level sandbox for AI agents built into Windows — gives enterprise security teams their first native, enforceable control plane for governing what autonomous agents can access, representing a critical architectural development CISOs should evaluate for inclusion in AI deployment standards.

📖 Read full article

TechCrunch Security · Jun 02 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Cyera's $12B valuation at an 80x ARR multiple — despite operating losses — reflects investor conviction that data security posture management is a must-have category in the AI era, giving CISOs negotiating leverage to accelerate DSPM budget conversations with finance leadership.

📖 Read full article

The Hacker News · Jun 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: An actively exploited zero-day with root privilege escalation in Cisco's SD-WAN platform — covering on-prem, cloud, and FedRAMP deployments — with no patch available demands immediate compensating controls; network segmentation and privileged access restrictions are the only mitigations today.

📖 Read full article

Dark Reading · Jun 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A second active exploit wave against PAN-OS GlobalProtect VPN means organizations running Palo Alto perimeter security face a compounding risk this week; with two active exploitation waves already observed, patching must be treated as a P0 incident response action.

📖 Read full article

Jordan: The week AI stopped being a security tool and started being a security problem. A Meta support bot hijacked Instagram accounts for the Obama White House. A self-replicating worm tore through Microsoft's own GitHub repos. And the NSA is reportedly weaponizing the same frontier model that fifteen countries just deployed to protect their critical infrastructure. If you're a CISO still treating AI as somebody else's risk category, this was the week that ended.

Alex: Welcome to Cleartext, the Saturday Week in Review. I'm Alex Chen, alongside Jordan Reeves. If you couldn't keep up this week, here's what mattered and what it means. We've got four big themes to work through. First, the AI trust paradox — the same model being deployed to defend critical infrastructure is simultaneously being weaponized for offensive operations. Second, supply chain integrity took a body blow this week, and I don't just mean one incident. Third, the espionage landscape is evolving in ways that should concern every CISO with cloud tenants or executive mailboxes. And fourth, the governance picture shifted meaningfully — budget cuts, a new executive order, and a landmark legal case that could reshape contractor accountability. Let's get into it.

Jordan: So let's start with what I'm calling the Mythos problem, because it really encapsulates where we are with frontier AI. On Monday, Anthropic announced the expansion of Project Glasswing — Claude Mythos Preview going to a hundred and fifty organizations across fifteen countries for critical infrastructure defense. Power grids, water systems, healthcare, communications. We're talking about infrastructure that touches a hundred million people. ENISA is on board through an EC-Anthropic bilateral agreement. This is real.

Alex: And then Thursday, we learn the NSA is reportedly preparing that same model for offensive cyber operations, despite a federal prohibition on engaging Anthropic as a vendor. Let that sink in. The same model being handed to European critical infrastructure operators to find vulnerabilities is being evaluated by the U.S. signals intelligence community to exploit them. For CISOs, the immediate question is: what does your risk model look like when a frontier AI model is simultaneously your defensive tool and your adversary's offensive weapon?

Jordan: And the benchmarks back this up. ExploitBench results published this week showed Mythos outperforming GPT-5.5 on Chrome vulnerability exploitation tasks. Anthropic's own internal analysis found eight hundred and thirty-two banned accounts misusing their systems over twelve months, with AI materially assisting low-skill attackers across multiple MITRE ATT&CK tactics. So we're not speculating about capability — it's measured.

Alex: Now tie this to the Meta story, because I think that's the connective tissue for the week. Krebs reported that Meta's AI support chatbot — a production agent, not a research prototype — was manipulated into resetting passwords and binding recovery emails to attacker-controlled addresses. The Obama White House Instagram, U.S. Space Force accounts, briefly defaced with pro-Iranian imagery. No malware. No credential theft. No prompt injection. The agent did exactly what it was designed to do. It just did it for the wrong people.

Jordan: Instructions circulated on Telegram before Meta patched. And here's the kicker — takeovers continued after an initial fix. This is the canonical example of what happens when you give an AI agent account-action authority without adversarial testing. Every CISO listening should be asking their teams on Monday: what AI-powered agents do we have in production, and what can they do to accounts, data, or access controls without a human in the loop?

Alex: Which brings us to Microsoft's MXC announcement at Build. Microsoft Execution Containers — an OS-level, policy-driven sandbox for AI agents, enforced at the kernel level. OpenAI and Nvidia are launch partners. This is the first real architectural answer to the agent authority problem. It's pre-deployment access scoping rather than reactive detection. I'd call it the most strategically important announcement of the week for enterprise security teams, even though it got less attention than the breaches.

Jordan: Agreed. It's the right design pattern. Whether the implementation holds up under adversarial pressure is another question, but at least someone is building the control plane. Now, let's talk supply chain, because this week was ugly.

Alex: The Miasma worm. Seventy-three Microsoft repositories compromised across four GitHub organizations — Azure, Azure-Samples, Microsoft, and MicrosoftDocs. GitHub had to disable access to the affected repos as containment. This is a self-replicating supply chain worm hitting Microsoft's own code repositories. Any code pulled from those repos during the infection window must be treated as potentially tainted. Full stop.

Jordan: And it wasn't isolated. A parallel campaign hit npm — IronWorm and a Miasma variant targeting over fifty legitimate packages. The payload is a Rust-based infostealer hiding behind an eBPF kernel rootkit. eBPF rootkits are particularly nasty because they operate at a level most endpoint detection tools aren't instrumented to catch. So you've got two major package ecosystems — GitHub and npm — simultaneously compromised with self-propagating malware. If your developers pulled anything from either ecosystem this week, your SBOM integrity is in question.

Alex: And the practical guidance here is uncomfortable. You need to validate your software bill of materials against the known compromised package lists. You need to check build pipeline logs for any pulls from affected Microsoft repos during the infection window. And frankly, if you don't have the tooling to do that quickly, this is the week that justifies the budget request.

Jordan: Let's pivot to espionage, because the Chinese activity this week deserves its own segment. UNC5221 — a Chinese espionage group — is now deploying two previously undocumented malware families, Plenet and AgentPSD, alongside the Brickstorm backdoor, specifically targeting Microsoft 365 environments. This is a capability upgrade designed for enterprise cloud tenants.

Alex: The shift to M365 targeting is significant because it means your primary defensive layer is identity security and conditional access policies, not network perimeter controls. If you're a CISO running M365, this week's action item is reviewing audit logs for anomalous OAuth consent grants, reviewing conditional access policies for gaps, and verifying that your identity provider configurations haven't been tampered with. Separately, TA4922 expanded phishing operations to the UK, Germany, Italy, and South Africa using ValleyRAT and Atlas RAT — so this isn't just one group. It's a coordinated broadening of Chinese targeting.

Jordan: And then there's the stock exchange espionage case. Unknown attackers — assessed as nation-state or state-sponsored — spent five months inside a senior stock exchange executive's Outlook mailbox. Five months. They copied the inbox in small batches, routed exfiltration through Dropbox and OneDrive so it blended with legitimate cloud traffic. Most DLP and SIEM configurations would miss this entirely. If you're in financial services, you need to ask whether your exfiltration detection can distinguish between a legitimate OneDrive sync and an attacker using OneDrive as a covert channel.

Alex: And connect that to the NATO Cyber Conflict conference reporting. The U.S. military admitted commercial location data was used to identify and target personnel during Operation Epic Fury. The implication the analysts drew — and I think it's correct — is that if nation-states are using commercial data broker information in wartime, China is almost certainly doing so in peacetime for corporate espionage targeting. CISOs need to understand that commercial data about their executives and key personnel is an intelligence commodity. It's being bought and analyzed.

Jordan: Now let's hit vulnerabilities quickly because there are two that demand action. CVE-2026-20245 — Cisco Catalyst SD-WAN Manager. CVSS 7.8, root privilege escalation, actively exploited, no patch available. Covers on-prem, cloud, and FedRAMP deployments. It can be chained with two other Cisco CVEs. Your only options right now are compensating controls — network segmentation and privileged access restrictions. There is no fix to apply.

Alex: And Palo Alto. CVE-2026-0257, PAN-OS GlobalProtect authentication bypass. Two distinct exploitation waves since mid-May, attack surface broadening. If you run Palo Alto at the perimeter, patching is a P-zero incident response action, not a scheduled maintenance task.

Jordan: Governance segment. Let's be efficient. The Trump administration released a scaled-back AI executive order — voluntary framework, significant industry concessions. A House AI bill proposes frontier model oversight but would preempt all state-level AI regulation. The practical read for CISOs: voluntary federal standards appear to be the ceiling for the foreseeable future. Build your AI governance program accordingly, but don't assume states won't push back on preemption.

Alex: CISA is facing a proposed two-hundred-fifty-million-dollar budget cut in FY2027 while simultaneously being assigned new AI security responsibilities. DHS Secretary Mullin says he wants six hundred more staff than CISA currently has. And Trump is reportedly considering Palantir's CTO to lead the agency. If you rely on CISA advisories, KEV catalog updates, or threat sharing, factor in reduced federal capability when planning your own detection and intelligence programs.

Jordan: And the IBM-AT&T False Claims Act lawsuit. A former IBM VP of threat intelligence alleging both companies concealed breaches and security control failures while holding major federal contracts. If this case gains traction, it establishes a new accountability framework under federal procurement law. Every CISO at a government contractor should be auditing their breach disclosure practices against FCA exposure right now.

Alex: Last item — Dashlane disclosed a brute-force attack that bypassed 2FA and resulted in encrypted vault downloads for fewer than twenty personal-plan users. The disclosure was criticized for opacity. If you have enterprise Dashlane deployments, verify whether any users are on personal subscription tiers and check master password strength policies.

Jordan: And Cyera's twelve-billion-dollar valuation at eighty times ARR — despite operating losses — tells you where investor money thinks the next critical category is. Data security posture management. Use that signal in your next budget conversation if you need DSPM tooling.

Alex: So stepping back — what defined this week? I'd say it was the week the AI agent attack surface became undeniable. We saw a production AI agent become the attack vector at Meta. We saw frontier models simultaneously deployed for defense and offense. We saw Microsoft propose the first real architectural answer with MXC. And we saw supply chain integrity shattered across two major ecosystems. The through-line is that AI is no longer adjacent to security — it is security. Every risk model, every control framework, every board presentation needs to reflect that.

Jordan: I'll add one thing. The convergence of nation-state espionage upgrading to cloud-native tooling, supply chain attacks becoming self-propagating, and AI agents operating with unchecked authority — these aren't three separate problems. They're three expressions of the same problem: we're deploying powerful autonomous systems faster than we're building the controls to govern them. That's the strategic conversation CISOs need to be having with their boards next week.

Alex: Well said. That's your week in review. The daily show returns Monday. Show notes and links to every story we covered are at cleartext.fm. Have a good weekend, everyone. Stay sharp.

Jordan: See you Monday.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 10 stories across 5 topic areas, including: China's TA4922 Expands Cybercrime Attacks Globally; CrowdStrike, Palo Alto Networks defy estimates as AI fuels cyber demand; AI is helping low-skill hackers pull off advanced cyberattacks.

Dark Reading · Jun 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A Chinese-linked threat group with a diverse, opportunistic attack portfolio is actively expanding its global footprint beyond East Asia, broadening the threat surface for enterprise organizations in Western markets. CISOs should update threat models and brief boards on China-linked cybercrime as a distinct risk category alongside state-sponsored espionage.

📖 Read full article

Cybersecurity Dive · Jun 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Strong earnings beats from the two largest independent cybersecurity platform vendors signal sustained enterprise security spending and validate AI-driven platform consolidation as a durable market dynamic — relevant for CISOs managing vendor contract negotiations and platform consolidation strategy. Board-level conversations about security budget justification are bolstered by sector-wide demand signals.

📖 Read full article

Help Net Security · Jun 05 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Anthropic's empirical analysis of 832 banned accounts demonstrates that AI is measurably lowering the skill floor for cyberattacks, with mapped MITRE ATT&CK coverage showing AI-assisted adversaries executing techniques previously requiring significant expertise. CISOs must accelerate threat model updates to account for a broader, less-skilled but more capable attacker population.

📖 Read full article

Help Net Security · Jun 05 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A credential-stuffing and brute-force attack against a major enterprise password manager resulted in exfiltration of encrypted vaults — a high-value target for offline cracking attacks that could eventually expose enterprise credentials at scale. CISOs using Dashlane for enterprise credential management should assess exposure and enforce MFA and strong master password policies.

📖 Read full article

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

Why it matters to CISOs: A breach of the UN World Food Programme's self-registration application exposing data on 600,000 conflict-zone households underscores the risks of humanitarian data systems as high-value espionage and disruption targets — relevant to any enterprise operating in geopolitically sensitive regions. Security leaders in NGO, government contractor, or multinational contexts should review data classification and access controls for sensitive population data.

📖 Read full article

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

Why it matters to CISOs: A supply-chain attack compromising 36 npm packages with infostealer malware represents a direct risk to enterprise development pipelines and any organization consuming affected open-source dependencies. CISOs should verify software composition analysis tooling is scanning for IronWorm indicators and ensure development environments are auditing npm dependencies.

📖 Read full article

CyberScoop · Jun 04 · Relevance: █████████░ 9/10

Why it matters to CISOs: A proposed $250M cut to CISA's budget would materially reduce the federal cyber defense and information-sharing apparatus that enterprises rely on for threat intelligence and critical infrastructure coordination. CISOs should reassess dependence on CISA services and accelerate private-sector threat sharing alternatives.

📖 Read full article

The Record (Recorded Future) · Jun 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The CISA director role has been vacant, and a Palantir CTO appointment would signal a significant philosophical and operational shift in how the agency approaches federal cybersecurity — with implications for public-private partnership models and AI-driven defense priorities. CISOs should monitor for changes in CISA's engagement posture and advisory outputs.

📖 Read full article

The Record (Recorded Future) · Jun 04 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The FTC's potential reversal of a landmark $150M privacy enforcement action signals a shift in the regulatory enforcement posture that enterprises have used to benchmark privacy program accountability. CISOs and legal teams should monitor whether this sets precedent for reduced enforcement risk or corporate restructuring as a penalty mitigation strategy.

📖 Read full article

Help Net Security · Jun 05 · Relevance: █████████░ 9/10

Why it matters to CISOs: An unpatched privilege escalation zero-day in Cisco Catalyst SD-WAN Manager is being actively exploited, putting enterprise WAN infrastructure at direct risk with no vendor fix currently available. CISOs running Cisco SD-WAN deployments must assess exposure and consider compensating controls immediately.

📖 Read full article

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

Jordan: And I'm Jordan Reeves. Let's get into it.

Alex: We have a packed show today. A Cisco SD-WAN zero-day with no patch and active exploitation. Two major CISA stories that, taken together, paint a pretty striking picture of where federal cyber defense is headed. A password manager breach that should make every CISO audit their vault strategy. Anthropic publishing hard data on AI-enabled attackers. China's TA4922 going global. And we'll touch on what the CrowdStrike and Palo Alto earnings tell us about where security budgets are actually going. Let's start where it hurts.

Jordan: Yeah, let's start with the one that's going to ruin someone's Friday. CVE-2026-20245. Privilege escalation zero-day in Cisco Catalyst SD-WAN Manager. No patch. Cisco has confirmed active exploitation in the wild.

Alex: And the details matter here. This isn't unauthenticated remote code execution. You need netadmin credentials on the box, or you need to chain it with one of two other CVEs, 20182 or 20127. So the attack surface is constrained, but constrained is not the same as safe.

Jordan: Right. If you're running Cisco SD-WAN, and a lot of enterprises are, you need to be asking your network team right now whether those two chaining CVEs are patched. Because if they're not, this becomes a much more accessible attack path. And netadmin credentials? In environments with weak credential hygiene, that's not a high bar.

Alex: Compensating controls. Segment your management plane. Audit who has netadmin access. Monitor for anomalous privilege changes. This is the kind of thing where you can't wait for the patch. You need to reduce exposure now and monitor aggressively.

Jordan: And frankly, if your SD-WAN management interface is reachable from anything other than a hardened jump box, we need to have a different conversation.

Alex: Agreed. Let's shift to Washington, because two stories out of the Hill this week are connected and they matter. First, House Appropriations is marking up FY2027 DHS funding today, Friday, with a proposed $250 million cut to CISA's budget. Democrats are loudly opposing it, but the markup is proceeding.

Jordan: And simultaneously, we learn that Shyam Sankar, the CTO of Palantir, is the leading candidate for the CISA director role, which has been vacant for a long time now.

Alex: Take these together. You have an agency that's already been losing staff and resources, now facing a quarter-billion-dollar cut, and the person being considered to lead it comes from a company whose entire model is large-scale data analytics and AI-driven intelligence. That's a philosophical pivot, not just a personnel change.

Jordan: Look, Sankar is a serious technologist. Palantir's platform capabilities are real. But leading CISA isn't a technology problem. It's a coalition problem. CISA's value to the private sector has been in its role as a neutral convener, a trusted information-sharing hub, the entity that coordinates across critical infrastructure sectors. If you shift that toward an AI-first, data-platform orientation, you potentially lose the trust that makes the sharing work.

Alex: And if you cut $250 million on top of that, you're not just changing direction, you're reducing capacity. For CISOs, the action item is concrete. You cannot assume CISA services you've relied on, KEV catalog maintenance, advisory quality, sector coordination, will continue at the same level. Start strengthening your private-sector threat sharing relationships. ISACs, direct vendor channels, peer networks. Diversify your intelligence inputs.

Jordan: This isn't speculative. The degradation has already started. This just accelerates it.

Alex: Now let's talk about a breach that hits enterprise credential management directly. Dashlane disclosed that attackers successfully accessed some customer accounts through credential stuffing and brute force, and they copied encrypted password vaults.

Jordan: This is the nightmare scenario for any password manager, and it's the second time we've seen it in the industry. The parallels to the LastPass incident are obvious. Dashlane says their internal systems weren't compromised. The attackers used valid or brute-forced user credentials to log into accounts and then exported the encrypted vaults.

Alex: So the vaults are encrypted. But they're now in the hands of attackers who can run offline cracking at their leisure. The strength of your master password is now the only thing standing between an attacker and every credential in that vault.

Jordan: And let's be honest about enterprise password manager deployments. How many organizations actually enforce master password complexity? How many have MFA on the vault itself, not just on SSO, but on the actual password manager authentication? In a lot of deployments, the answer is not enough.

Alex: If you're a Dashlane enterprise customer, the response is immediate. Force master password resets. Enforce MFA if you haven't. Audit which accounts were affected. And start rotating credentials stored in those vaults, especially service accounts and privileged access credentials. Don't wait for Dashlane to tell you whether your specific tenant was hit.

Jordan: And this is a good moment for any CISO to stress-test their password manager deployment regardless of vendor. What happens if vaults are exfiltrated? How strong are your master passwords? Is your threat model current?

Alex: Let's pivot to the AI threat landscape, because Anthropic dropped something genuinely useful this week. They published an analysis of 832 accounts they banned for malicious cyber activity between March 2025 and March 2026, and they mapped the observed behaviors to MITRE ATT&CK.

Jordan: This is the kind of empirical data the industry has been missing. We've had a lot of hand-waving about AI lowering the bar for attackers. Anthropic is showing the receipts. And what the data shows is that low-skill actors are using AI to execute attack techniques that previously required significant expertise. We're talking about things like defense evasion, lateral movement, credential access, stages that used to require real tradecraft.

Alex: The strategic implication is clear. Your threat model's assumption about attacker capability needs to shift. The population of actors who can execute a competent attack chain just got larger. Not because individual tools got better, but because AI is bridging the skill gap.

Jordan: And this connects directly to volume. More capable attackers means more attacks that get past the initial filter. Your SOC is going to see more sophisticated-looking activity from actors who, two years ago, would have been stopped at the phishing stage. The middle of the funnel is getting fatter.

Alex: Which brings us to budget. CrowdStrike and Palo Alto both beat earnings estimates this week, driven by AI-related security demand. The narrative that AI tooling would cannibalize traditional security spend? The market just rejected it.

Jordan: Enterprise security budgets are expanding, not reallocating. And the platform consolidation trend is real. Both companies are benefiting from CISOs who want fewer vendors doing more, with AI capabilities baked in rather than bolted on.

Alex: For CISOs heading into budget season or mid-year reviews, this is useful ammunition. The market is validating that security spend is increasing, not contracting. If your CFO is pushing back on security investment, the earnings data from the two largest independent platform vendors says demand is accelerating. Use it.

Jordan: Now, on the threat actor front, let's talk about TA4922. Dark Reading reported this week that this Chinese-linked cybercrime group is expanding globally beyond its traditional East Asian footprint.

Alex: What makes TA4922 interesting and dangerous is that they're described as one of the most diverse and least-focused cybercrime groups operating. They're opportunistic. They don't have a narrow targeting profile, which means the probability of incidental compromise goes up for enterprises that never considered themselves targets of Chinese-linked cybercrime.

Jordan: And I want to emphasize the word cybercrime here, not espionage. We've trained boards to think about China-linked threats in terms of intellectual property theft and state-sponsored espionage. TA4922 is a financially motivated operation. It's a different risk category, and it needs to be briefed that way. Chinese-linked cybercrime is distinct from Chinese state-sponsored espionage, and your board needs to understand both.

Alex: The geographic expansion also signals operational maturity and possibly increased resourcing. This isn't a scrappy crew anymore. They're scaling.

Jordan: Two more stories to touch on quickly. The UN World Food Programme disclosed a breach of its self-registration application for Palestine, exposing data on 600,000 Gaza households. For most of our listeners, this isn't a direct operational concern. But if you're in the NGO space, government contracting, or any multinational operating in conflict zones, this is a signal. Humanitarian data systems are high-value targets, and they're often under-resourced from a security perspective.

Alex: And on the supply chain front, 36 npm packages were compromised with a new infostealer malware called IronWorm. If your development teams are consuming open-source dependencies, and they are, make sure your software composition analysis tooling is scanning for IronWorm indicators. Infostealers in dev environments can harvest credentials, tokens, and source code. This is pipeline hygiene.

Jordan: One more. The FTC is considering setting aside or modifying the $150 million privacy penalty against X, formerly Twitter. X is arguing the order was issued against a company that no longer exists. If the FTC accepts that reasoning, it creates a template for using corporate restructuring to escape legacy enforcement orders.

Alex: That's a precedent every privacy and legal team should be watching. If rebranding and restructuring become viable strategies for shedding regulatory obligations, it changes the calculus for enforcement accountability across the board.

Jordan: All right, looking at the week as a whole, what's the thread?

Alex: The thread this week is that the assumptions underpinning your security program are shifting faster than most organizations are updating them. Attacker skill floors are dropping because of AI. A major federal cyber defense agency is being simultaneously defunded and restructured. Your password vaults might be in someone else's hands. And a Chinese cybercrime group you've never briefed your board on is now operating in your geography. The common action is the same across all of these. Revisit your assumptions. Update your threat models. Don't coast on last year's risk assessment.

Jordan: And don't assume the cavalry is coming from Washington. Build your own resilience. Strengthen your private-sector relationships. Test your controls against the threat landscape as it actually exists today, not as it existed when you last updated your strategy deck.

Alex: That's the show for Friday, June 5th. Show notes and links to every story we covered are at cleartext.fm. Have a good weekend. Stay sharp.

Jordan: See you Monday.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 4 topic areas, including: Srsly Risky Biz: NATO's cyber approach needs to change; CISA warns of cyberattacks targeting fuel tank monitoring systems; China-Linked TA4922 Expands Phishing Attacks to UK, Germany, Italy, and South Africa.

Risky Business News · Jun 04 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The admission that US military used commercial location data to target personnel in Iran operations confirms that commercial data brokers pose direct national security risks—enterprises holding or purchasing similar data face elevated espionage and targeting risk from adversary intelligence services.

📖 Read full article

BleepingComputer · Jun 03 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A multi-agency advisory covering active attacks on internet-exposed automatic tank gauge systems across energy, agriculture, and transportation sectors requires CISOs at critical infrastructure organizations to immediately audit OT/ICS internet exposure and assess ATG system inventory.

📖 Read full article

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

Why it matters to CISOs: A newly attributed China-linked threat group rapidly expanding operations across major European economies and South Africa signals broadening PRC espionage targeting of Western enterprise organizations, warranting updated threat intelligence briefings for multinational security teams.

📖 Read full article

BleepingComputer · Jun 03 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: OFAC sanctions on Iran's largest crypto exchange for facilitating ransomware payments signal continued US pressure on Iranian cyber threat actors and expand compliance obligations for any enterprise with cryptocurrency exposure or Iran-adjacent transaction monitoring requirements.

📖 Read full article

The Hacker News · Jun 04 · Relevance: █████████░ 9/10

Why it matters to CISOs: A five-month undetected intrusion into a C-suite Outlook mailbox at a major global stock exchange—with exfiltration disguised as normal cloud traffic via Dropbox and OneDrive—is a direct case study in detection gap risk for executive email accounts and cloud-blended exfiltration techniques.

📖 Read full article

TechCrunch Security · Jun 03 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A midyear retrospective covering a DOGE data breach, critical energy and water system compromises, and an FBI surveillance system hack provides CISOs with essential board-level context for threat landscape briefings and benchmarking their own program posture.

📖 Read full article

CyberScoop · Jun 03 · Relevance: ████████░░ 8/10

Why it matters to CISOs: CISA's staffing trajectory directly affects the agency's capacity to support critical infrastructure operators, issue advisories, and respond to incidents—CISOs reliant on CISA resources need to calibrate their dependency on federal cybersecurity support accordingly.

📖 Read full article

Dark Reading · Jun 03 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Widening policy exclusions—including potential gaps for social engineering attacks like ClickFix—mean CISOs must re-examine their cyber insurance coverage assumptions and ensure risk transfer strategies account for the evolving exclusion landscape.

📖 Read full article

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

Why it matters to CISOs: A critical Cisco Unified Communications Manager vulnerability with public PoC exploit code enabling root privilege escalation demands urgent patching prioritization, as Unified CM is pervasively deployed across enterprise voice and collaboration infrastructure.

📖 Read full article

Alex: It's Thursday, June 4th, 2026. This is Cleartext. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: So Jordan, you want to start us off with the one that's been sitting with you since this morning?

Jordan: Yeah. Someone sat inside a stock exchange executive's Outlook mailbox for five months. Five months of reading every email, every attachment, every calendar invite. And nobody noticed. Because they were smart about it—they siphoned the data out in tiny batches through Dropbox and OneDrive, so it just looked like normal cloud traffic. Symantec and Carbon Black's Threat Hunter Team published the attribution this week. This is espionage, not a money grab. And it's exactly the kind of intrusion that should terrify every CISO listening to this show.

Alex: Five months. And this wasn't some mid-level analyst's inbox. This was a senior executive at a major global stock exchange. The kind of person whose emails contain market-moving information, regulatory correspondence, board communications. That's the crown jewels.

Jordan: Right. And the tradecraft here is what matters. They didn't exfil a giant PST file at two in the morning. They dripped it out over sanctioned cloud platforms that every enterprise already whitelists. Your DLP is looking for anomalies. This wasn't anomalous. It was designed to look exactly like someone syncing their work files to the cloud. If you're a CISO and your executive email monitoring relies on volumetric triggers or endpoint alerts alone, this is your wake-up call.

Alex: And I'll say it plainly—most organizations do not monitor C-suite mailboxes with the intensity this threat demands. There's a cultural reluctance. Executives don't want to feel surveilled. But the adversary knows that, and they exploit it. If you haven't had the conversation with your CEO about why their inbox needs the same security scrutiny as a production database, today is the day.

Jordan: Agreed. And honestly, this connects to a bigger theme we're going to hit several times today, which is the commercial data and cloud infrastructure that enterprises use every day being weaponized against them.

Alex: Perfect segue. Let's talk about the NATO story, because Risky Business broke down something this week that I think is going to reshape how a lot of security leaders think about data broker risk.

Jordan: So the US military confirmed—and this is on the record now—that commercial location data was used to identify and target personnel involved in Epic Fury, the US military operation against Iran. Let me be precise about what that means. You could buy data from a broker that tells you where specific phones are, when, and how often. And the US military used exactly that kind of data for operational targeting.

Alex: Which means every sophisticated adversary can do the same thing.

Jordan: Exactly. And the analysis from Tom Uren at Risky Business makes the point I've been making for years—China is almost certainly exploiting these same commercial data flows right now, in peacetime, for counter-intelligence and espionage. They don't need to hack anything. They can just buy it.

Alex: So for the CISO audience, here's the translation. If your enterprise is purchasing, holding, or processing commercial location data, you are holding intelligence-grade targeting information. The risk calculus on that data just changed. It's not just a privacy liability anymore. It's an espionage magnet. Your data governance framework needs to reflect that.

Jordan: And on the NATO side, allies are re-evaluating their collective cyber posture. The conference made clear that the current frameworks aren't keeping pace with how cyber operations are actually being conducted—not by adversaries, but by allies. There's a real reckoning happening about what offensive cyber means when it's built on top of commercial infrastructure.

Alex: Let's stay in the geopolitical lane because there's a cluster of stories that belong together. CISA, FBI, NSA, and the Department of Energy jointly issued a warning this week about active attacks on automatic tank gauge systems. These are the OT systems that monitor fuel and liquid storage tanks across energy, agriculture, and transportation.

Jordan: And the vector is embarrassingly simple. These systems are internet-exposed. Not theoretically. Actually. Right now. Someone can find them on Shodan in about thirty seconds. And threat actors are actively targeting them.

Alex: If you're a CISO at a critical infrastructure organization and you haven't done a comprehensive audit of your OT and ICS internet exposure in the last ninety days, this advisory is your mandate. A four-agency joint advisory is not a suggestion. It's a flare.

Jordan: The frustrating thing is we've been talking about internet-exposed OT for a decade. And yet here we are with a multi-agency advisory because the problem persists. The gap is almost never technical. It's organizational. OT teams and IT security teams still don't have unified asset inventories. You can't protect what you can't see, and in a lot of these environments, the CISO literally does not know these systems exist on the network.

Alex: Meanwhile, TA4922—a newly attributed China-linked group—has expanded phishing operations into the UK, Germany, Italy, and South Africa. The operational tempo is described as rapid, and their tooling includes ValleyRAT, Atlas RAT, and previously undocumented malware families.

Jordan: This is the PRC broadening its aperture. For years, the primary targets were US defense industrial base and Asia-Pacific. Now they're going after European enterprise organizations with purpose-built tooling that keeps evolving. If you're running a multinational security team, your threat model for European operations needs updating. TA4922 is well-resourced, adaptive, and clearly has tasking that extends beyond the usual suspects.

Alex: And rounding out the geopolitical picture, OFAC sanctioned Nobitex—Iran's largest cryptocurrency exchange—for facilitating ransomware payments and terrorist financing.

Jordan: This is the Treasury continuing to tighten the financial noose around Iranian cyber actors. For CISOs, the practical implication is compliance. If you have any cryptocurrency exposure, any Iran-adjacent transaction monitoring, the OFAC list just got longer. And the penalties for getting this wrong are severe. Make sure your compliance team has updated their screening.

Alex: Let's shift to governance, because there are two stories that I think every CISO needs to weigh together. First, DHS Secretary Mullin told Congress he wants about 600 more staff for CISA than the agency currently has.

Jordan: Which sounds like good news until you realize that even with those 600 people, CISA would still be well below its pre-2025 staffing levels. This is a partial restoration, not a comeback.

Alex: And that matters because a lot of security programs—especially in critical infrastructure—have built real dependencies on CISA's advisory services, incident response support, and vulnerability coordination. If CISA is operating at reduced capacity, you need to know that. You need to calibrate your assumptions about what federal support looks like if you get hit.

Jordan: It's not that CISA is going away. It's that the response times will be longer, the advisories might be thinner, and the hands-on support in a crisis may not materialize the way it did three years ago. Plan accordingly.

Alex: The second governance story pairs with that perfectly. Cyber insurance premiums are dropping, but exclusions are widening. Insurers are getting more aggressive about carving out coverage for social engineering attacks—including ClickFix-style campaigns, which are among the most prevalent attack techniques right now.

Jordan: So your premium goes down and your board thinks you're saving money. But the fine print now says that the attack most likely to actually hit you isn't covered. That's not a good trade.

Alex: It's a terrible trade. And I've seen this pattern before. CISOs present their cyber insurance renewal to the board, everyone's happy about the lower premium, and nobody reads the exclusion schedule. Then an incident happens, the claim gets denied, and suddenly the CISO is answering very uncomfortable questions. Read your policy. Read the exclusions. Bring your broker into a room with your threat intel team and map the exclusions against your actual risk profile. If there's a gap, you need to know before the incident, not after.

Jordan: I'd add—if your insurer is excluding social engineering, that tells you something about the loss data they're seeing. They're not excluding it because it's rare. They're excluding it because it's expensive and frequent.

Alex: Quick hit on the vulnerability front. Cisco patched a critical-severity flaw in Unified Communications Manager. Root privilege escalation, and proof-of-concept exploit code is already public.

Jordan: If you run Unified CM—and a lot of enterprises do because it's the backbone of their voice and collaboration infrastructure—patch this now. Public PoC means the exploitation timeline just collapsed. This is not a "schedule it for the next maintenance window" situation.

Alex: Agreed. Prioritize it today.

Jordan: So Alex, when I look across everything we covered—the stock exchange mailbox compromise, commercial data weaponization, OT systems exposed to the internet, expanding Chinese espionage operations—there's a theme.

Alex: There is. The common thread is that the infrastructure enterprises rely on every day—cloud platforms, commercial data, OT systems, even their voice infrastructure—is the attack surface. The adversary isn't trying to break through the wall anymore. They're living in the house.

Jordan: And the detection paradigm most organizations have deployed was built for the wall-breaking model. Perimeter alerts, volumetric anomalies, signature-based detection. That executive's mailbox was compromised for five months because the exfiltration looked like normal work. Commercial location data is being used for targeting because it's legally purchased and openly available. Tank gauge systems are being attacked because they were never supposed to be on the internet in the first place.

Alex: So the watch item for the rest of this week and into next—if you haven't done a comprehensive review of what your organization considers "normal" cloud traffic, normal data flows, normal OT exposure, you're operating on assumptions that the adversary has already mapped and is exploiting. The CISOs who are going to have a good second half of 2026 are the ones who challenge those assumptions right now.

Jordan: Well said.

Alex: That's our show for Thursday, June 4th. Show notes and links to every story we covered are at cleartext.fm. We'll be back tomorrow.

Jordan: See you then.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 6 topic areas, including: AI-built ransomware toolkit automates EDR evasion, AD discovery; China Uses Dual-Method Cyberattack on Czech Orgs; Anthropic scales Claude Mythos to critical infrastructure in 15+ countries.

BleepingComputer · Jun 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: An AI-generated ransomware toolkit that autonomously discovers Active Directory topology and evades EDR solutions represents a qualitative escalation in attacker capability that directly threatens enterprise security architectures built around endpoint detection as a last line of defense.

📖 Read full article

Dark Reading · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: China's double-layer spear-phishing campaign deploying Azureveil malware against Czech and Taiwan-linked organizations demonstrates active expansion of state-sponsored targeting into European enterprise targets, requiring CISOs in multinational firms with EU or Taiwan-facing operations to reassess their threat model.

📖 Read full article

TechCrunch Security · Jun 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Anthropic's expansion of AI-assisted vulnerability discovery to 150 critical infrastructure organizations across 15 countries signals that AI-powered offensive security tooling is being institutionalized at national scale — CISOs in energy, water, healthcare, and communications need to understand both the defensive opportunity and the model-access risk surface this creates.

📖 Read full article

TechCrunch Security · Jun 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: Enterprise organizations relying on Dashlane for credential management face immediate credential exposure risk; the breach of MFA-protected password vaults raises urgent questions about third-party password manager risk in enterprise environments and vendor due diligence.

📖 Read full article

Dark Reading · Jun 03 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A sustained, months-long compromise of a senior finance executive's email inbox at a global stock exchange using living-off-the-land techniques is a direct signal to CISOs in financial services that email monitoring and privileged-account behavioral analytics gaps are being actively exploited at the highest levels.

📖 Read full article

CyberScoop · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The White House AI executive order shapes the federal AI governance landscape that enterprise security programs must align to, particularly around confidentiality, cybersecurity, insider risk, and IP protection requirements for AI model access — CISOs advising on AI deployment policy need to understand the new regulatory baseline.

📖 Read full article

TechCrunch Security · Jun 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Cyera's near-$300M raise at an $12B valuation underscores how enterprise demand for data security posture management (DSPM) is driving outsized investment — CISOs evaluating vendor stability and market consolidation should track whether this capital positions Cyera as an acquisition target or category definer.

📖 Read full article

The Hacker News · Jun 03 · Relevance: █████████░ 9/10

Why it matters to CISOs: This vulnerability affects nearly every major enterprise web server and reverse proxy in default configuration, enabling unauthenticated remote denial-of-service at scale — CISOs running internet-facing infrastructure on NGINX, Apache, IIS, or Envoy should treat this as an emergency patching priority.

📖 Read full article

The Hacker News · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Oracle WebLogic is deeply embedded in enterprise Java environments and financial services middleware — CISA's KEV listing confirms active exploitation of this unauthenticated remote takeover flaw, making immediate remediation a compliance obligation for federal contractors and a critical priority for all enterprise WebLogic deployments.

📖 Read full article

Alex: Welcome to Cleartext. It's Wednesday, June 3rd, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Alex, I want to start today with something that should make every CISO in our audience pause. Dashlane, the password manager, confirmed that attackers brute-forced their two-factor authentication system and downloaded complete customer password vaults. Let that sit for a second. The thing your organization deployed specifically to reduce credential risk just became the single point of failure.

Alex: Yeah, and that's where we're going to spend real time today. We've also got an AI-built ransomware toolkit that's automating Active Directory discovery and EDR evasion in production — not a lab demo, not a proof of concept. We'll cover a new HTTP/2 vulnerability that hits basically every web server you're running in default config. China expanding its targeting into European enterprises. A months-long email compromise at a global stock exchange. The new White House AI executive order. Anthropic scaling its vulnerability discovery program to critical infrastructure across fifteen countries. And Cyera's eye-popping twelve billion dollar valuation. Let's get into it.

Jordan: So let's start with Dashlane because this is not just a breach story. This is a vendor trust story. Attackers found a way to brute-force Dashlane's two-factor authentication implementation. Not phish it, not social-engineer it — brute-force it. Which immediately raises the question of what rate limiting, what lockout policies, what anomaly detection was sitting in front of that 2FA system.

Alex: And this is the nightmare scenario we've been warning about with centralized credential stores. The pitch for enterprise password managers has always been: consolidate credentials, enforce complexity, reduce reuse. And that's valid. But the implicit assumption is that the vault itself is inviolable. When it's not, you haven't reduced risk. You've concentrated it. Every corporate credential stored in those vaults — SaaS applications, internal systems, privileged accounts — is now potentially exposed.

Jordan: The immediate action here is obvious. If your organization uses Dashlane, you're rotating credentials. All of them. Today. But the strategic question is harder. Do you move to a different password manager and hope their 2FA implementation is better? Do you accelerate your passwordless roadmap? This is a board-level conversation about single points of failure in your identity architecture.

Alex: And it's a vendor due diligence conversation. When was the last time your team actually tested your password manager's authentication controls? Not took the vendor's word for it — actually tested them. I'd bet most organizations haven't. This should change that calculus permanently.

Jordan: Staying on the theme of trust assumptions breaking down, let's talk about the AI-built ransomware toolkit that BleepingComputer reported on. A threat actor is deploying a toolkit that uses AI to automate Active Directory discovery and EDR evasion. This is not somebody prompting ChatGPT to write a script. This is a production attack toolkit where AI is compressing the entire reconnaissance and evasion phase of the attack lifecycle.

Alex: This matters because most enterprise security architectures are built on a fundamental assumption: that there's a window between initial access and lateral movement where your detection stack can catch the attacker. EDR is supposed to be that safety net. Active Directory monitoring is supposed to give you visibility into reconnaissance. This toolkit is specifically designed to shrink that window to near zero and blind your detection at the same time.

Jordan: Right. The AD discovery piece is particularly concerning. Traditional ransomware operators spend time mapping the domain — finding domain controllers, identifying high-value targets, understanding trust relationships. That reconnaissance generates noise. It's detectable. When you automate that with AI that understands AD topology natively, you eliminate the fumbling around that gives defenders their edge.

Alex: So what do you do? First, this reinforces that EDR alone is not a strategy. If your security architecture's last line of defense is endpoint detection, you are already behind this threat. You need network-level segmentation that limits lateral movement regardless of whether the attacker is detected. You need identity-based controls that don't rely on catching the reconnaissance. And honestly, you need to pressure-test your detection stack against AI-generated evasion, not just the known bypass techniques from last year.

Jordan: And this connects directly to the HTTP/2 Bomb vulnerability, which is a different kind of problem but equally urgent. Researchers — and notably, this was discovered using OpenAI Codex — found a remote denial-of-service vulnerability that affects NGINX, Apache, IIS, Envoy, and Cloudflare Pingora. In their default HTTP/2 configurations. Default configurations, Alex. That means if you stood up a web server and didn't specifically harden the HTTP/2 settings, you're exposed.

Alex: The blast radius here is enormous. These are the web servers and reverse proxies that sit in front of virtually every enterprise web application. And because it's unauthenticated — no credentials needed — any internet-facing deployment is a target. This is an emergency patching priority. No debate. If your team hasn't already started assessing exposure across your HTTP/2-enabled infrastructure, that starts this morning.

Jordan: I want to flag something else about this one. It was discovered by AI — Codex chaining vulnerability analysis to find something humans had missed across multiple server implementations. We're seeing AI accelerate both offense and defense simultaneously. The toolkit we just talked about uses AI to automate attacks. This vulnerability was found by AI doing defensive research. That duality is the defining feature of the threat landscape we're entering.

Alex: While we're on vulnerabilities, the Oracle WebLogic CVE that just hit CISA's Known Exploited Vulnerabilities catalog. CVE-2024-21182. Unauthenticated network-level takeover, CVSS 7.5. If you're running WebLogic — and if you're in financial services or large enterprise Java environments, you probably are — the KEV listing means active exploitation is confirmed. For federal contractors, you have mandatory remediation deadlines. For everyone else, treat it the same way.

Jordan: WebLogic is one of those platforms that's deeply embedded in middleware stacks. It's not always visible to the security team. So step one is actually confirming your inventory. You might have WebLogic instances your team doesn't even know about.

Alex: Let's shift to the geopolitical picture. Jordan, China's dual-method campaign targeting Czech organizations and Taiwan-linked entities.

Jordan: This is significant because of the targeting expansion. Chinese state-linked actors deploying Azureveil malware through a layered spear-phishing campaign — that's sophisticated but not surprising. What's notable is the deliberate targeting of Czech organizations. We're seeing China's cyber operations extend deeper into European enterprise targets, not just the traditional Asia-Pacific theater. If you're a multinational with EU operations, particularly any business that touches Taiwan — supply chain, trade, diplomatic, anything — you need to update your threat model. The assumption that Chinese state targeting is primarily an APAC problem is no longer valid.

Alex: And the dual-method, layered attack chain is designed specifically to frustrate attribution and complicate incident response. This is the kind of campaign that lives in your environment for months if you're not looking for it.

Jordan: Which brings us perfectly to the stock exchange compromise. A threat actor maintained near-continuous access to a senior finance executive's email inbox at a global stock exchange for months. Using living-off-the-land techniques. No custom malware. Just native Windows tools.

Alex: This is the story that should terrify financial services CISOs. Not because of the technique — living-off-the-land is well understood — but because of the duration. Months of access to a senior executive's email. That's deal flow, regulatory correspondence, board communications, M&A discussions. The data exfiltration potential is staggering.

Jordan: And the detection failure is the real lesson. Signature-based detection doesn't catch this. If your privileged account monitoring isn't doing behavioral analytics — looking at login patterns, email access volumes, geographic anomalies — you have a blind spot that sophisticated actors are actively exploiting. This isn't theoretical. This happened at a globally influential financial institution with presumably a mature security program.

Alex: Quick pivot to governance. The White House released its scaled-back AI executive order yesterday. Jordan, the headline is that it's more industry-friendly than earlier drafts.

Jordan: It includes cybersecurity requirements, insider-risk provisions, and IP protection mandates for federal AI model access. But the concessions to industry are significant. Near-term compliance burden is lighter than what was circulating in earlier drafts. For CISOs, the practical implication is downstream. If you're a federal contractor or in critical infrastructure, these requirements will flow into your procurement and deployment policies. Start mapping your AI governance program to this framework now, even if enforcement timelines are generous.

Alex: And speaking of AI in critical infrastructure, Anthropic is expanding Project Glasswing — their vulnerability discovery program using the Claude Mythos model — to 150 organizations across fifteen-plus countries in power, water, healthcare, and communications. Infrastructure potentially affecting a hundred million people. There are security requirements organizations must meet before they get access to the model, but the scale here is remarkable. AI-powered offensive security tooling is being institutionalized.

Jordan: The dual-use question is real. Every one of those organizations gets access to a model that's exceptional at finding vulnerabilities. The defensive value is obvious. But the model-access risk surface — who has access, how it's secured, what happens if credentials leak — that's a new attack vector CISOs in those sectors need to account for.

Alex: Last one before we look ahead. Cyera, the data security posture management company, is nearing a three hundred million dollar raise at a twelve billion dollar valuation. That's an eighty-times ARR multiple despite operating losses.

Jordan: That's the market telling you something. Investors believe data security posture management is a generational category. Whether Cyera specifically justifies that valuation is a different question, but CISOs should be tracking this space. DSPM is becoming board-level priority, and the consolidation dynamics over the next eighteen months will determine which vendors survive and which get absorbed.

Alex: Alright, looking ahead. Jordan, the thread running through today's episode is obvious. AI is simultaneously the attack tool, the vulnerability discovery engine, the governance challenge, and the investment thesis. The Dashlane breach shows that even foundational security controls can't be taken for granted. The AI ransomware toolkit shows attackers compressing kill chains faster than most enterprises can adapt their detection. And the HTTP/2 Bomb shows AI finding vulnerabilities at scale across critical infrastructure.

Jordan: The theme for the rest of this week and into next: assumption testing. Every defensive assumption in your architecture — that EDR will catch lateral movement, that your password manager is secure, that your executive email monitoring is sufficient, that your web servers are hardened — every one of those needs to be validated against current threat reality, not last year's. The attackers have new tools. If your defensive assumptions haven't been updated to match, you're operating on borrowed time.

Alex: That's the show for today. Show notes and links to every story we covered are at cleartext.fm. I'm Alex Chen.

Jordan: I'm Jordan Reeves. We'll see you tomorrow.

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

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: NSA selects new leads for key cybersecurity posts; Sophos uncovers AI-powered malware lab built for EDR evasion; Microsoft launches MXC, an OS-level sandbox for AI agents, with OpenAI and Nvidia already on board.

The Record (Recorded Future) · Jun 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Leadership transitions at NSA's Cybersecurity Directorate and Cybersecurity Collaboration Center are directly relevant to CISOs who depend on public-private threat intelligence sharing — new leadership may shift priorities and partnership engagement models.

📖 Read full article

Help Net Security · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The discovery of a threat actor using AI to systematically build and test EDR evasion frameworks signals that endpoint detection controls must be stress-tested against AI-assisted bypass techniques — reliance on EDR as a primary detection layer carries increasing residual risk.

📖 Read full article

VentureBeat Security · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: OS-level policy enforcement for AI agent execution addresses one of the most pressing enterprise AI governance gaps — CISOs evaluating agentic AI deployment strategies need to assess MXC as a potential foundational control layer for Windows-based AI workloads.

📖 Read full article

VentureBeat Security · Jun 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A 31.5% prompt injection success rate against Anthropic's browser agent — the highest figure disclosed by any frontier lab — gives CISOs a concrete risk benchmark for agentic AI deployments and underscores the need for mandatory prompt injection testing before production rollout.

📖 Read full article

TechCrunch Security · Jun 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Enterprise password manager breaches carry outsized third-party risk — any organization with Dashlane deployed in their stack must assess exposure and review vendor security controls immediately. The 2FA brute-force vector signals a systemic authentication weakness relevant to all enterprise credential tooling decisions.

📖 Read full article

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

Why it matters to CISOs: A supply-chain compromise of 30+ official Red Hat npm packages directly threatens enterprise CI/CD pipelines and developer build environments — organizations using Red Hat Cloud Services tooling must audit dependency integrity and check for credential exfiltration immediately.

📖 Read full article

Krebs on Security · Jun 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: This incident is a live case study in AI chatbot prompt injection enabling account takeover at scale — CISOs must evaluate whether their own enterprise AI support and helpdesk automation tools carry analogous social-engineering and account-reset vulnerabilities.

📖 Read full article

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

Why it matters to CISOs: With NVD's unprocessed backlog doubling to 27,000+ vulnerabilities, CISOs can no longer rely on the NVD as a timely authoritative source — this demands a formal reassessment of vulnerability intelligence workflows and investment in alternative enrichment sources.

📖 Read full article

CyberScoop · Jun 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: Active exploitation of a Palo Alto Networks flaw affecting perimeter infrastructure demands immediate triage across all enterprise deployments — the fact it initially appeared low-severity before escalating is a critical lesson in patch prioritization and vendor advisory monitoring.

📖 Read full article

Alex: Welcome to Cleartext. It's Tuesday, June 2nd, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. Let's get into it.

Alex: We have a packed show today. A password manager breach that hinges on a 2FA brute-force, which should make every CISO rethink their credential tooling assumptions. A supply-chain attack on Red Hat npm packages that's hitting developer pipelines right now. Microsoft's new OS-level sandbox for AI agents. And Anthropic publishing a number that should be uncomfortable for everyone building agentic AI. Plus, the NVD is officially broken — an inspector general said so — and a Palo Alto Networks flaw that everyone ignored until it was too late. Jordan, let's start with the story you flagged.

Jordan: Yeah, the Sophos finding. They discovered a threat actor who built what amounts to an AI-powered malware R&D lab. Not just using AI to write malicious code — that's old news at this point. This actor built a dedicated testing framework, using AI coding tools, specifically designed to develop and iterate EDR evasion techniques. They were running Cobalt Strike profiles tuned to disguise beacon traffic as legitimate web requests, with command and control running over Telegram. Sophos found it after an anomalous endpoint in a customer environment triggered alerts from a testing directory. So this actor was literally doing QA on their evasion techniques inside a compromised environment.

Alex: And this is the part that should land hard for CISOs. If you're treating EDR as your primary detection layer — and let's be honest, a lot of organizations do — this finding says your adversaries are now systematically stress-testing your controls with AI assistance before they deploy. The development cycle for evasion has compressed dramatically. You need to be running your own adversary simulation against your EDR stack at a cadence that matches this reality. If your last purple team exercise was six months ago, you're behind.

Jordan: And it's not just the sophistication. It's the accessibility. You don't need nation-state resources to build one of these labs anymore. AI coding tools have democratized the process. A motivated mid-tier threat actor can iterate on EDR bypasses the way a startup iterates on product features.

Alex: Which connects directly to two AI stories we need to cover. Microsoft announced MXC at Build 2026 — Microsoft Execution Containers. This is an OS-level sandbox that controls what AI agents can access and do on a Windows system. OpenAI and Nvidia are launch partners, so this has immediate ecosystem weight.

Jordan: The timing here is telling. For two years the industry has been racing to make AI agents more capable without building the guardrails to match. MXC is Microsoft saying: we're going to enforce policy at the OS layer, not just at the application layer. IT admins get hard boundaries on agent behavior — file access, network calls, system modifications. It's the control plane that's been missing.

Alex: For CISOs evaluating agentic AI deployment strategies, especially on Windows-based workloads, MXC should be on your architecture review immediately. It doesn't solve everything, but it's the first credible attempt at foundational policy enforcement for agents at the OS level. The question is how granular the policies are and how quickly the ecosystem builds around it.

Jordan: And then pair that with the Anthropic disclosure. Their red teamers hijacked Claude's browser agent via prompt injection 31.5 percent of the time before safeguards kicked in. That is the highest figure any frontier lab has publicly disclosed.

Alex: Now, here's the nuance. Anthropic published a 244-page safety report covering four agentic surfaces. OpenAI, Google, Meta — none of them gave comparable data. So Anthropic's number looks like a liability, but it's actually the most transparent data point we have. The real problem is that the other labs aren't telling you their numbers.

Jordan: Exactly. And for CISOs doing procurement on agentic AI tooling, you can't do comparative risk assessment when only one vendor is showing you the data. So what do you do? You mandate prompt injection testing in your own environment before anything goes to production. Period. Thirty-one percent is a useful benchmark, but your mileage will vary based on your deployment context.

Alex: And the Meta story from Krebs underscores why this matters in practice right now. Attackers circulated instructions on Telegram showing how to trick Meta's AI support bot into resetting Instagram account passwords. The Obama White House account and the U.S. Space Force Chief Master Sergeant's account were both briefly defaced with pro-Iranian content. Meta has patched it, but the exploit spread virally before they did.

Jordan: This is prompt injection in the wild, against a production AI system, enabling account takeover at scale. If you've deployed AI chatbots for helpdesk, support, or account management, you need to be asking right now: can someone talk my bot into resetting a password or escalating privileges? Because that's exactly what happened here.

Alex: Let's shift to the breaches. The Dashlane story first. Hackers brute-forced Dashlane's two-factor authentication system to access customer accounts and download encrypted password vaults. Fewer than 20 personal subscription accounts were affected, so the blast radius is limited. But the vector is what matters here.

Jordan: If a password manager's 2FA can be brute-forced, that's a systemic design flaw, not a configuration issue. For enterprise CISOs, the immediate action is: if you have Dashlane in your stack, assess your exposure now. But the broader question is whether your credential management vendor has rate-limiting and lockout controls on their MFA that would survive a sustained brute-force attempt. Ask them. Get it in writing.

Alex: And the Red Hat supply-chain attack. More than 30 npm packages under Red Hat's '@redhat-cloud-services' namespace were compromised after a Red Hat employee's GitHub account was hijacked. A new malware variant called Miasma was injected to steal credentials from developer build environments. Malicious commits were pushed on June 1st across two separate time windows, so this was deliberate and coordinated.

Jordan: This is a textbook supply-chain attack against trusted packages in a trusted namespace. If your developers are pulling from '@redhat-cloud-services,' you need to audit dependency integrity right now. Check your build logs for commits from June 1st. And this is another argument for reproducible builds, dependency pinning, and runtime integrity verification in your CI/CD pipeline. Trust is not a security control.

Alex: The point about trusted namespaces is critical. Developers see Red Hat and assume safety. That assumption is exactly what the attackers exploited.

Jordan: Moving to vulnerabilities. CVE-2026-0257 in Palo Alto Networks products is now confirmed under active exploitation. What makes this one worth flagging is the trajectory. It was initially rated low severity. It flew under the radar. And now it's being actively exploited against perimeter infrastructure.

Alex: This is the patch prioritization lesson we keep having to relearn. Low CVSS scores don't mean low risk. If it's on your perimeter, if it's on infrastructure that faces the internet, you treat it differently. Your vulnerability management program needs context-aware prioritization, not just severity scores. And if you're running Palo Alto products, triage this today.

Jordan: Which brings us to the NVD story, and this one has been building for a long time. An inspector general report found that NIST's National Vulnerability Database backlog grew from 13,000 unprocessed vulnerabilities in February 2024 to over 27,000 by the end of 2025. The IG's words were that the failures are "undermining the NVD's utility and public trust."

Alex: This is not a surprise to anyone who's been watching, but having the IG put it on the record matters. The NVD has been the foundational data source for vulnerability management across the entire industry. If you're still relying on NVD as your primary or sole enrichment source, you are working with incomplete data. You need to be investing in alternative or supplementary vulnerability intelligence — commercial feeds, vendor advisories, CISA KEV. The NVD is no longer timely enough to be your single source of truth.

Jordan: And for CISOs going to the board, this is worth mentioning. The government's own authoritative vulnerability database is officially degraded. That changes the risk equation for any program that was built on NVD as a foundational control.

Alex: One more story before we look ahead. NSA has formalized leadership at two key cyber units. David Imbordino is now permanent chief of the Cybersecurity Directorate, and Bruce Jones takes over the Cybersecurity Collaboration Center, which is the unit that works most directly with private sector enterprises on threat intelligence sharing.

Jordan: The CCC appointment is the one CISOs should care about. If you're participating in any of NSA's private-sector threat intelligence programs, new leadership typically means new priorities and potentially new engagement models. It's worth reaching out to your contacts there proactively.

Alex: Alright, looking ahead. Jordan, what's the through-line today?

Jordan: The through-line is the collapse of assumptions. Your EDR is being systematically tested by AI-powered adversaries. Your trusted open-source packages aren't trustworthy. Your password manager's 2FA can be brute-forced. Your government vulnerability database is broken. Your AI chatbot can be talked into resetting passwords. Every one of these stories is about a control or a trust relationship that CISOs assumed was solid, and it's not. The theme for the rest of this year is going to be re-validating your foundational assumptions, not just adding new tools on top of them.

Alex: Agreed. And the Microsoft MXC announcement and the Anthropic disclosure point to the same thing from the builders' side. The industry is starting to acknowledge that you have to build the controls in, not bolt them on. Whether that's OS-level agent sandboxing or publishing your actual prompt injection failure rates, the move toward honesty and architectural rigor is the right one. CISOs should be rewarding that transparency in their procurement decisions.

Jordan: Watch for follow-on activity from the Red Hat supply-chain compromise this week. If they got credentials from developer build environments, the secondary effects haven't played out yet.

Alex: That's the show for Tuesday, June 2nd. Show notes and links to every story we covered are at cleartext.fm. I'm Alex Chen.

Jordan: I'm Jordan Reeves. See you tomorrow.

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

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