Cleartext

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 10 stories across 5 topic areas, including: China-Linked UAT-7810 Expands ORB Network With New LONGLEASH Malware; What Happens if China Hacks the US Water Supply? I Went to a Secret War Game to Find Out; Hacked, leaked, and held for ransom: The worst breaches of 2026 so far.

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

Why it matters to CISOs: China's active expansion of its Operational Relay Box infrastructure through compromised networking devices indicates a persistent, growing capability to proxy malicious traffic through enterprise edge devices — organizations must audit internet-facing routers and network appliances for signs of compromise.

📖 Read full article

Wired Security · Jul 08 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A closed-door Volt Typhoon war game involving insurers surfaced critical gaps in cyber incident response for critical infrastructure disruption scenarios — CISOs in sectors with OT/ICS exposure or insurance dependencies should examine the scenario's findings for their own resilience planning.

📖 Read full article

TechCrunch Security · Jul 07 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: A mid-year retrospective covering the most damaging incidents of 2026 — including DOGE data exposure, critical energy and water system hacks, and an FBI surveillance system breach — provides essential context for board reporting and benchmarking program priorities against actual threat patterns.

📖 Read full article

BleepingComputer · Jul 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Accenture's confirmed breach involving source code, RSA and SSH keys, and Azure access tokens raises third-party supply chain risk concerns for any enterprise with Accenture as a technology services partner, requiring immediate review of shared credential and access arrangements.

📖 Read full article

Infosecurity Magazine · Jul 08 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Documented adversarial use of agentic AI compressing a cloud attack lifecycle from weeks to 72 hours fundamentally changes incident response planning assumptions — detection and containment SLAs built around human-speed attacks are now dangerously outdated.

📖 Read full article

The Hacker News · Jul 07 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Active M365 device-code phishing campaigns bypassing traditional credential-page detection represent a direct threat to enterprise identity infrastructure — CISOs should validate that conditional access policies and user awareness programs account for legitimate-flow abuse tactics.

📖 Read full article

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

Why it matters to CISOs: The EU's new cybersecurity communication anchored around AI sovereignty will likely shape procurement requirements, vendor due diligence standards, and regulatory expectations for enterprises operating in European markets — CISOs should assess exposure to forthcoming AI sourcing mandates.

📖 Read full article

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

Why it matters to CISOs: DHS Inspector General scrutiny of forced CISA staff reassignments adds to concerns about the operational capacity and independence of the US federal cybersecurity authority — CISOs relying on CISA threat intelligence, advisories, and coordination should factor in the agency's diminished capacity when planning.

📖 Read full article

The Hacker News · Jul 08 · Relevance: █████████░ 9/10

Why it matters to CISOs: A privilege escalation flaw requiring no special permissions affecting virtually every mainstream Linux distribution since 2011 poses existential risk to enterprise server fleets, cloud workloads, and container environments — emergency patching prioritization required across the estate.

📖 Read full article

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

Why it matters to CISOs: A 16-year-old Linux kernel vulnerability enabling full VM escape on Intel and AMD hardware threatens the hypervisor isolation that enterprise cloud and on-premises virtualization security models depend on — this demands immediate assessment of patching status across all virtualized infrastructure.

📖 Read full article

Jordan: A fifteen-year-old Linux kernel flaw lets any logged-in user take root with zero special permissions. Every mainstream distro since 2011. And that's not even the only ancient Linux kernel bug dropping today — there's a separate sixteen-year-old flaw enabling full VM escape on Intel and AMD. If you run Linux anywhere — and you do — today's episode is not optional.

Alex: Welcome to Cleartext for Wednesday, July 8th, 2026. I'm Alex Chen, alongside Jordan Reeves. We've got a packed show. Two critical Linux kernel vulnerabilities that together threaten basically everything from your container fleet to your hypervisor boundaries. China's APT infrastructure is growing in ways that should change how you think about IP-based detection. Accenture confirmed a breach that puts its entire client base on notice. And we have documented evidence of agentic AI compressing attack timelines from weeks to three days. Plus, the EU is making moves on AI sovereignty that will reshape procurement for anyone doing business in Europe. Let's get into it.

Jordan: Let's start with the two Linux vulnerabilities because they're both genuinely critical and they compound each other. GhostLock, CVE-2026-43499 — disclosed by Nebula Security. This is a privilege escalation flaw in the Linux kernel. It requires nothing exotic. Any authenticated user, no special permissions, no unusual configuration, gets full root. It's been sitting in every mainstream distro since 2011. Fifteen years.

Alex: And the blast radius here is what makes this a board-level conversation. This isn't a niche component. This is default kernel code shipping in Ubuntu, Red Hat, Debian, SUSE — everything. Your on-prem servers, your cloud workloads, your container hosts. And speaking of containers, GhostLock enables container escape, which means your multi-tenant Kubernetes environments, your shared cloud infrastructure — the isolation boundaries you're depending on are compromised.

Jordan: Then layer on Januscape. Separate vulnerability, sixteen years old, also in the Linux kernel. This one enables VM escape on both Intel and AMD hardware. So if GhostLock breaks your container isolation, Januscape breaks your hypervisor isolation. Together, these two vulnerabilities attack the two fundamental containment models that modern infrastructure relies on.

Alex: The action here is straightforward but urgent. This is an emergency patching cycle. If you're a CISO listening to this, you need your infrastructure team treating both of these as P-zero today. Not this sprint, not next maintenance window. And if you're in a cloud environment, you need to be pressing your providers — AWS, Azure, GCP — for confirmation that their host kernels are patched. Don't assume it.

Jordan: And for the detection side — GhostLock requires only a logged-in user. That means any compromised service account, any low-privilege foothold an attacker already has, instantly becomes root. Your threat models around lateral movement and privilege escalation just changed.

Alex: Let's pivot to the geopolitical picture because there's a clear through-line today. Jordan, walk us through UAT-7810 and what the ORB network expansion means.

Jordan: So UAT-7810 is a Chinese APT that maintains and grows something called the LapDogs ORB network. ORB stands for Operational Relay Box. Think of it as a distributed proxy network built from compromised legitimate devices — in this case, primarily unpatched Ruckus routers sitting on enterprise network edges. They've developed new malware called LONGLEASH specifically to expand this network. Cisco Talos has been tracking this campaign since at least June 2025, and it's actively evolving.

Alex: And for CISOs, the strategic implication is significant. ORB networks defeat IP-based detection and attribution. When the attack traffic hitting your environment originates from what looks like a legitimate enterprise router in a normal geography, your threat intel feeds, your geo-blocking, your IP reputation systems — they all fail. This is China building persistent, distributed infrastructure that makes their operations harder to detect and nearly impossible to attribute through traditional means.

Jordan: Exactly. And this connects directly to the second China story. Wired reported on a closed-door war game simulating Volt Typhoon attacks on US water systems. This wasn't a think tank exercise. Insurers were in the room, stress-testing their exposure models against coordinated critical infrastructure disruption. The scenario produced burst water mains and hospital evacuations. And the finding was stark — existing response frameworks and insurance models are simply not calibrated for nation-state coordinated attacks on critical infrastructure.

Alex: This matters to CISOs in two dimensions. First, if you have OT or ICS exposure, the scenario modeling coming out of these exercises should feed directly into your resilience planning. Second — and this is the one people miss — the insurance implications. If your cyber insurance policy has exclusions or sub-limits around acts of war or nation-state attacks, and insurers are actively war-gaming their exposure to exactly these scenarios, expect coverage terms to tighten. You need to be having that conversation with your broker now, not after an incident.

Jordan: The TechCrunch mid-year retrospective reinforces all of this. The worst breaches of 2026's first half include DOGE-related data exposure, energy and water infrastructure compromises, and the breach of an FBI surveillance system. The pattern is unmistakable — government and critical infrastructure are under sustained, escalating pressure from both nation-states and ransomware operators. If you're preparing a board update for Q3, this retrospective is useful source material for contextualizing your own risk posture against the broader landscape.

Alex: Now let's talk about Accenture, because this has immediate third-party risk implications for a very large number of enterprises. The threat actor known as 888 claims to have stolen thirty-five gigabytes of data including source code, RSA keys, SSH keys, Azure personal access tokens, and Azure Storage access keys. Accenture has confirmed the breach, though the full scope remains unclear.

Jordan: This is a supply chain risk story. Accenture is embedded in the technology infrastructure of a significant portion of the Fortune 500. If stolen credentials include access tokens and keys tied to client environments — and the claimed data types strongly suggest they could — then downstream compromise is a real possibility. This isn't theoretical. Those Azure personal access tokens and storage keys could provide direct access to client cloud resources.

Alex: If Accenture is a services partner for your organization, the action is immediate. Review every shared credential arrangement, every service account, every access token that connects your environment to theirs. Rotate anything that could be compromised. And have a direct conversation with your Accenture account team about whether your environment is in scope. Don't wait for their notification.

Jordan: Let's talk about the Sygnia report on agentic AI in attacks, because this one fundamentally changes operational assumptions. They documented a real-world case — not a lab exercise, not a proof of concept — where an attacker used agentic AI to compress what would normally be a weeks-long cloud compromise into seventy-two hours. Automated reconnaissance, lateral movement, exploitation — all at machine speed.

Alex: This is the story I'd flag for every CISO thinking about their SOC's detection and response SLAs. If your mean time to detect is measured in days and your mean time to contain is measured in additional days, you are now operating slower than your adversaries' automated tooling. The assumption that you have a window — that human attackers take time to orient, to make mistakes, to move cautiously — that assumption is eroding fast.

Jordan: And to be clear, this isn't some hypothetical future concern. This is happening now. The Sygnia case is documented. The tooling exists. The question isn't whether agentic AI will be used offensively — it's whether your defensive automation can match the tempo. For most organizations, honestly, the answer today is no.

Alex: Staying on the identity and access front — the DEBULL tooling campaign is worth sixty seconds because it's clever and it's actively running. This exploits Microsoft's legitimate device-code authentication flow. No fake login page. The attacker sends a collaboration-themed lure — looks like a Teams invite, a SharePoint share — and it pushes the user into the real Microsoft device login experience. The user authenticates against Microsoft's actual infrastructure, and the attacker captures the token.

Jordan: This is hard to detect because there's no malicious infrastructure to block. It's Microsoft's own authentication flow. Your phishing detection that keys on fake login pages misses this entirely. CISOs need to validate that conditional access policies restrict device-code flow to managed devices only, and that user awareness training covers this specific scenario. It's an active campaign running since late June.

Alex: Two governance items to close the segments. The European Commission adopted a formal communication on July 7th aimed at reducing reliance on foreign AI in cybersecurity contexts. Three pillars — making frontier AI safe and accessible for European cybersecurity, preparing the EU's cyber ecosystem, and scaling European AI capabilities. This is regulatory direction, not regulation yet, but it signals where procurement requirements and vendor due diligence standards are heading for anyone operating in European markets.

Jordan: And the DHS Inspector General has opened an investigation into forced reassignments of CISA personnel. I'll be direct — if you rely on CISA for threat intelligence, advisories, or coordination during incidents, you should be factoring in diminished operational capacity. The agency's independence and staffing are under pressure, and that has practical implications for the quality and timeliness of the support you can expect.

Alex: Alright, Jordan, looking at today's stories together — what's the emerging theme?

Jordan: The theme is that the assumptions underlying most security architectures are being invalidated simultaneously. Kernel isolation — broken by GhostLock and Januscape. IP-based detection — defeated by ORB networks. Human-speed attack timelines — obsoleted by agentic AI. Credential-page phishing detection — bypassed by device-code flow abuse. Hypervisor boundaries — compromised by VM escape. Every one of these is a foundational assumption that security programs are built on, and every one of them took a hit today.

Alex: And the meta-point for CISOs is that this isn't about any single vulnerability or technique. It's about the rate at which your defensive model's core assumptions are being challenged. The question for every security leader this week is — when was the last time you stress-tested your architecture against the failure of its own foundational assumptions? Not individual controls, but the assumptions those controls are built on. Container isolation works. VMs are isolated from hosts. Attackers move at human speed. IP reputation is meaningful. If those assumptions fail, does your program still hold?

Jordan: That's the conversation to have with your team this week. Not just patch GhostLock — though do that immediately — but what else are we assuming that might not be true anymore?

Alex: That's our show for Wednesday, July 8th. Show notes and links to every story we covered are at cleartext.fm. I'm Alex Chen.

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

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-07-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 9 stories across 5 topic areas, including: Suspected Chinese espionage group used a Roundcube exploit chain to burrow into universities; Canadian spy agency reports hacking three criminal groups in 2025; Sysdig clocks first documented case of agentic ransomware.

CyberScoop · Jul 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: China-aligned actors actively targeting physics and engineering departments at U.S. and Canadian universities signals an ongoing IP-theft campaign that enterprises in defense-adjacent and advanced manufacturing sectors should treat as an indicator of parallel targeting against their own research and development environments.

📖 Read full article

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

Why it matters to CISOs: Canada's CSE publicly disclosing offensive cyber operations against a ransomware-as-a-service gang sets a notable precedent for allied nation offensive disruption of cybercriminal infrastructure, a trend CISOs should factor into threat landscape assessments for ransomware group longevity and retaliation risk.

📖 Read full article

CyberScoop · Jul 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: The first documented case of an AI agent autonomously executing core ransomware attack steps signals a qualitative shift in threat actor capabilities that will compress response windows and require security programs to re-examine detection and IR assumptions.

📖 Read full article

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

Why it matters to CISOs: A breach exposing Social Security numbers and health data for nearly 4 million individuals at a major medical device manufacturer highlights ongoing third-party and OT/medical sector supply chain risk, with significant HIPAA and state notification obligations likely at play.

📖 Read full article

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

Why it matters to CISOs: The extradition and prosecution of Scattered Spider members marks continued law enforcement pressure on the group responsible for high-profile retail and enterprise breaches, relevant context for CISOs assessing the ongoing threat from this collective and the legal accountability framework for cybercrime.

📖 Read full article

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

Why it matters to CISOs: A guest-to-host VM escape in Linux KVM directly threatens cloud and virtualized infrastructure at enterprise scale — any organization running KVM-based hypervisors on Intel or AMD must treat this as a priority patch given the public PoC that already causes host kernel panics.

📖 Read full article

BleepingComputer · Jul 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: Active exploitation of a CVSS 10.0 ColdFusion vulnerability days after patch release and within minutes of a public PoC underscores the urgency for organizations running ColdFusion in enterprise web application environments to patch immediately or isolate exposed instances.

📖 Read full article

The Hacker News · Jul 07 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Critical pre-authentication bypass flaws in BeyondTrust's privileged remote access products — core PAM infrastructure at many enterprises — represent a high-priority patch given the product's privileged position and BeyondTrust's prior exploitation history in 2024-2025.

📖 Read full article

Dark Reading · Jul 06 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A new memory disclosure flaw in Citrix NetScaler being actively exploited within days of a public PoC mirrors the 2023 CitrixBleed incident that caused widespread enterprise compromise — CISOs with NetScaler deployments should treat this as an emergency patching scenario.

📖 Read full article

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

Jordan: And I'm Jordan Reeves. Alex, I want to start with something that should make every CISO sit up. Sysdig has documented what they're calling the first confirmed case of agentic ransomware in the wild. An AI agent, not a human operator, handled the technical execution of a ransomware attack end to end. We've been talking about this theoretically for two years. It's not theoretical anymore.

Alex: That is where we're going to spend some real time today. We've also got a sixteen-year-old KVM vulnerability that lets guest VMs escape to the host, active exploitation of a max-severity ColdFusion flaw and a new NetScaler memory disclosure bug that's giving everyone CitrixBleed flashbacks. On the geopolitical side, Chinese espionage actors are hitting university physics departments through Roundcube, and Canada's spy agency just publicly admitted to hacking a ransomware gang. Lots to cover. Let's get into it.

Jordan: So let's start with JadePuffer, which is what Sysdig is calling this agentic ransomware incident from late June. Here's the setup. A human threat actor initiated the campaign, but the AI agent handled the actual technical execution. It exploited a Langflow vulnerability, exfiltrated data, and encrypted systems. The human set the objective. The machine did the work.

Alex: And that's the part that matters for defense. We're not talking about AI generating better phishing emails or writing malware faster. We're talking about an autonomous agent making real-time decisions during an intrusion. Reconnaissance, lateral movement, data staging, encryption. The compression of the attack timeline is the immediate operational concern. If your mean time to detect is measured in hours, you may already be too late against something that operates in minutes.

Jordan: Right. And I want to be precise here because the hype machine is going to run wild with this. The agent didn't do everything. Sysdig was clear about that. A human still had to point it at a target and kick it off. But the barrier to entry just dropped dramatically. You no longer need a skilled operator to execute the technical chain. You need someone who can prompt an agent and aim it.

Alex: Which means the population of people who can execute a sophisticated ransomware attack just expanded by orders of magnitude. For CISOs, the practical implication is twofold. First, your detection logic needs to account for attack patterns that don't look human. No pauses, no typos in commands, no coffee breaks between steps. Second, your incident response playbooks need to assume compressed timelines. If you're still planning for a six-hour window between initial access and encryption, revisit that assumption.

Jordan: And honestly, this also changes the math on automated response. The argument against automated containment has always been the risk of false positives disrupting business. But if the attacker is an agent moving at machine speed, your human-in-the-loop response model may simply be too slow. That's a conversation boards need to have.

Alex: Agreed. This is a board-level conversation about risk tolerance for automated defensive action. Let's shift to the vulnerability landscape because this is a heavy week. Jordan, walk us through the KVM flaw.

Jordan: CVE-2026-53359, they're calling it Januscape. It's a use-after-free bug in the shadow MMU code in Linux KVM. It affects both Intel and AMD x86 platforms. And it has been sitting there for sixteen years. A public proof of concept crashes the host kernel from inside a guest VM. The researcher claims a separate unreleased exploit achieves full code execution on the host.

Alex: So for anyone running KVM-based virtualization, which is a significant portion of enterprise infrastructure and a huge chunk of cloud providers, this is a guest-to-host escape. That breaks the fundamental isolation guarantee of virtualization. In multi-tenant environments, this is existential.

Jordan: Exactly. If you're a cloud customer, you're relying on your provider's hypervisor isolation. If you're running your own KVM infrastructure, you need to patch now. The public PoC is enough to cause denial of service. The full exploit, if it surfaces, gives an attacker in any guest VM root on the host and access to every other VM on that box.

Alex: If you're running KVM in production, this is your priority this week. Full stop. Now, ColdFusion. CVE-2026-48282, CVSS ten point zero.

Jordan: Max severity. Adobe patched it June 30th. WatchTowr published technical analysis on July 2nd. Exploitation was detected within minutes. Not hours. Minutes. This is the new normal for high-value vulnerabilities. The window between patch and exploit is effectively zero for anything with a public PoC.

Alex: And ColdFusion is still running in a lot of enterprise web application environments. More than people realize. If you haven't inventoried your ColdFusion instances, today's the day. If you can't patch immediately, isolate them from the internet. This is not one you can schedule for the next maintenance window.

Jordan: And then we have NetScaler. Another memory disclosure flaw being actively exploited after a PoC dropped. The headline from Dark Reading says it all: CitrixBleed-ing Again. Same product family, same pattern. PoC publishes, attackers weaponize it almost instantly.

Alex: For CISOs who lived through the original CitrixBleed in 2023, you know what this looks like at scale. Mass compromise of VPN infrastructure. Credential theft. Persistent access. If you have NetScaler in your environment, treat this as an emergency. And if you went through CitrixBleed the first time, dust off that incident playbook because the response pattern is going to be very similar.

Jordan: And rounding out the vulnerability segment, BeyondTrust patched CVE-2026-40138, a pre-authentication bypass in Remote Support and Privileged Remote Access. CVSS nine point two. Unauthenticated attackers can take control of the device.

Alex: BeyondTrust products sit at the absolute center of privileged access in many enterprises. And this is the same vendor that was exploited in the Treasury Department breach in late 2024. Given that history and the pre-auth nature of this flaw, prioritize this alongside KVM and ColdFusion. Four critical vulnerabilities in one week, all requiring immediate action. Your patching teams are going to need support.

Jordan: Let's pivot to geopolitics. Proofpoint published research on a suspected China-aligned group exploiting Roundcube vulnerabilities to compromise physics and engineering departments at U.S. and Canadian universities. The Roundcube CVE they used, CVE-2024-42009, is a nine point three. They're stealing credentials and they're specifically targeting STEM research.

Alex: This is textbook Chinese state IP theft, and it's been going on for decades. But the targeting tells you what Beijing is interested in right now. Physics and engineering departments doing research in areas that map directly to military and advanced manufacturing applications. If you're a CISO at a defense contractor, an advanced materials company, a semiconductor firm, a national lab, treat this as a signal that you are either already being targeted or you're next in the queue.

Jordan: The Roundcube angle is interesting too. This isn't a zero day. These are known vulnerabilities in webmail infrastructure that a lot of universities simply haven't patched. The barrier to entry for this campaign is low. The intelligence value of what they're stealing is enormous. That asymmetry is exactly what makes state-sponsored espionage so effective.

Alex: And for enterprise CISOs, the supply chain angle matters. If you're collaborating with universities on research, if you have joint ventures, if your engineers are adjunct faculty, those university email systems are now a vector into your intellectual property.

Jordan: Shifting to Canada. CSE, their signals intelligence agency, publicly disclosed in their annual report that they conducted offensive cyber operations against a ransomware-as-a-service gang in 2025. They also hit an online extremist group and drug traffickers.

Alex: This is significant for a couple of reasons. First, it's a Five Eyes ally publicly acknowledging offensive operations against criminal infrastructure. That's still rare. The U.S. and UK have done it, but Canada being this transparent about it normalizes the practice across the alliance.

Jordan: Second, and this is the part CISOs should think about, when governments hack ransomware gangs, those gangs sometimes retaliate. Not against the government, because that's hard, but against softer targets. We saw that dynamic after Colonial Pipeline when the U.S. went after DarkSide infrastructure. The group fragmented and its members showed up in other operations. Disruption is good. But disruption creates chaos, and chaos creates unpredictable threat actor behavior.

Alex: That's a nuanced point. Law enforcement disruption is net positive for the ecosystem. But it doesn't eliminate the operators. It scatters them. And scattered, angry operators sometimes escalate.

Jordan: Let's quickly hit the breach and the Scattered Spider extradition. Nearly four million individuals notified by a major medical device manufacturer. SSNs and health data exposed. The company says no evidence of public exposure, but four million notification letters is four million notification letters.

Alex: HIPAA obligations, state notification laws, inevitable class actions. For CISOs in healthcare and medtech, this is a reminder that the regulatory and legal exposure from a breach of this scale is enormous. And for everyone else, if this company is in your supply chain, you need to understand what data of yours they held.

Jordan: And a Scattered Spider member, dual U.S.-Estonian citizen, extradited to the U.S. on charges related to hacking a luxury retailer. The interesting forensic detail is the FBI traced him using a Windows device ID. Basic operational security failure on his part.

Alex: Scattered Spider has been one of the most disruptive threat groups targeting enterprise environments. The continued prosecutions are good. But the group is loosely organized, and taking out individual members doesn't necessarily degrade their capability. CISOs should continue to treat Scattered Spider TTPs, particularly social engineering of help desks and SIM swapping, as active threats.

Jordan: Alright, Alex, let's look at the bigger picture this week. What's the thread that ties these stories together?

Alex: Speed. Every story this week is about compression. The time between patch and exploit is now minutes. AI agents are compressing attack execution from hours to minutes. State actors are running campaigns against known vulnerabilities that organizations simply haven't patched fast enough. The defensive model that assumes you have time, time to assess, time to schedule, time to respond, that model is breaking.

Jordan: And I'd add that the attack surface is getting more consequential, not just broader. KVM hypervisors, BeyondTrust PAM, NetScaler VPNs, ColdFusion web apps. These aren't edge cases. These are foundational infrastructure components. When these break, everything behind them is exposed.

Alex: So the action item for this week is honest self-assessment. How fast can your organization actually patch a critical vulnerability? Not theoretically. Actually. If the answer is more than seventy-two hours for internet-facing infrastructure, you have a gap that this week's threat landscape will punish.

Jordan: And if you're not already modeling AI-assisted attacks in your tabletop exercises, add JadePuffer to the scenario list. The future just showed up.

Alex: That's our show for Tuesday, July 7th. Show notes and links to every story we covered are at cleartext.fm. I'm Alex Chen.

Jordan: I'm Jordan Reeves. Stay sharp out there.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 4 topic areas, including: Risky Bulletin: EU official’s phone infected with Pegasus; Canadian spy agency says it hacked drug traffickers, extremists and a ransomware gang last year; Suspected China-Nexus Hackers Use Fake Indian Tax Filing Utility to Deploy DcRAT.

Risky Business News · Jul 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: Pegasus infections of elected officials signal continued aggressive use of commercial spyware against high-value targets, raising direct concerns for CISOs protecting executives, board members, and government-facing personnel who may be similarly targeted.

📖 Read full article

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

Why it matters to CISOs: Government offensive cyber operations against ransomware gangs provide strategic context for CISOs on how allied intelligence services are disrupting threat actors, which may temporarily affect the operational tempo of specific ransomware groups.

📖 Read full article

The Hacker News · Jul 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: China-nexus espionage campaigns targeting corporate finance teams via tax authority impersonation are directly relevant to CISOs at multinationals with India operations, highlighting the need for spear-phishing controls around regulatory compliance workflows.

📖 Read full article

The Record (Recorded Future) · Jul 06 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: Russia's escalating targeting of media organizations extends the information warfare threat surface and is relevant to CISOs at media, publishing, and broadcast companies, as well as organizations in industries frequently covered by adversarial state media narratives.

📖 Read full article

Infosecurity Magazine · Jul 06 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The emergence of agentic AI-powered ransomware represents a qualitative escalation in attacker capability that CISOs must factor into incident response planning and AI governance frameworks, as autonomous agents could dramatically compress attack timelines.

📖 Read full article

The Hacker News · Jul 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: As enterprises rapidly adopt AI coding agents, SkillCloak demonstrates that existing static analysis controls are insufficient to detect malicious agent plugins, forcing CISOs to rethink supply chain security for the AI agent ecosystem.

📖 Read full article

Help Net Security · Jul 06 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: With guest accounts comprising 69% of monitored SaaS accounts and persistent OAuth grants creating orphaned access paths, CISOs face a measurable and growing SaaS identity hygiene problem that requires updated third-party access governance policies.

📖 Read full article

BleepingComputer · Jul 06 · Relevance: █████████░ 9/10

Why it matters to CISOs: A maximum-severity ColdFusion vulnerability under active exploitation requires immediate attention from CISOs whose organizations run ColdFusion-based web applications or legacy enterprise portals, as unpatched instances face direct compromise risk.

📖 Read full article

Alex: Welcome to Cleartext for Monday, July 6th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves. So, researchers just published what they're calling the first fully agentic ransomware. JadePuffer. Autonomous AI agents handling recon, lateral movement, encryption, the whole chain, no human in the loop. If that doesn't rearrange your Monday priorities, I don't know what will. We'll get to that.

Alex: We've got a packed show today. Pegasus is back in the headlines, this time infecting a European parliamentarian's phone. Canada's signals intelligence agency just went public about hacking a ransomware gang. There's a China-nexus campaign targeting corporate finance teams in India. We've got a max-severity ColdFusion zero-day under active exploitation. And we'll talk about why your SaaS guest accounts might be your biggest blind spot. Let's get into it.

Jordan: Let's start with the spyware story because it connects to something every CISO should be thinking about right now. A European Member of Parliament's phone was confirmed infected with Pegasus. NSO Group's flagship product, still in active use, still landing on high-value targets.

Alex: And this is the part that should make CISOs uncomfortable. If you're protecting executives who interact with government officials, board members with political exposure, anyone in a regulated industry that intersects with geopolitics, you are in the blast radius of commercial spyware. This isn't hypothetical.

Jordan: The targeting logic has broadened. It used to be dissidents and journalists. Now it's elected officials in EU member states. The implication for the private sector is straightforward. If your CEO is meeting with a defense ministry official, or your general counsel is advising on sanctions compliance, their devices are plausible targets for state-aligned commercial spyware.

Alex: And this is where I'd push CISOs to have a real conversation with their boards about mobile threat defense. Not the checkbox version. Actual device attestation, behavioral anomaly detection on mobile endpoints, and honest policies about what devices executives carry into sensitive meetings. Most organizations still treat mobile as a second-class citizen in their security architecture.

Jordan: One related data point from the same bulletin. Android is dropping its PIN brute-force limit from 1,800 attempts to 20. That's a massive reduction. It signals that even the platform vendors are acknowledging that physical device compromise is a real and present threat.

Alex: Good. That's overdue. Let's shift to offensive cyber, because Canada just made some noise.

Jordan: CSE, Canada's signals intelligence agency, publicly disclosed in its annual report that it conducted offensive cyber operations against a ransomware gang, drug traffickers, and extremist groups last year. This is notable not because Five Eyes countries haven't been doing this, but because they said it out loud.

Alex: And the strategic read for CISOs is important. Allied governments are actively disrupting ransomware infrastructure. That's a tailwind for defenders, but it's an unpredictable one. You might see a ransomware group go dark for a few weeks, and the reason might be a government operation you'll never hear the full details of.

Jordan: Right. Don't build your risk model around it, but understand that the threat landscape isn't purely organic. There are state hands on the scale. And the more that Five Eyes normalizes public disclosure of these operations, the more deterrent value they carry. It also raises the bar for ransomware operators who now have to worry about offensive capabilities from multiple allied intelligence services, not just the FBI.

Alex: Which brings us to China-nexus activity. Operation DragonReturn, attributed to a suspected Chinese threat actor, is targeting Indian taxpayers, tax professionals, and corporate finance teams with spear-phishing emails that impersonate India's Income Tax Department. They're delivering DcRAT, a remote access trojan designed to exfiltrate sensitive financial data.

Jordan: The tradecraft here is bread and butter, but the targeting is strategic. Tax season lures impersonating a legitimate regulatory body, aimed at people whose jobs require them to open exactly these kinds of documents. If you're a multinational with India operations, your finance and compliance teams are the attack surface here.

Alex: And the lesson is broader than India. Every jurisdiction has regulatory compliance workflows that create predictable, exploitable moments. Tax filings, audit cycles, regulatory submissions. Attackers know when your people are most likely to click on something that looks official. CISOs should be mapping those calendars and layering additional controls during peak periods. Extra scrutiny on inbound attachments, tighter sandboxing, targeted user awareness campaigns timed to those windows.

Jordan: Now let's talk about Russia and Ukraine. A top Ukrainian security official disclosed two previously unreported attacks on TV media organizations and said Russian hackers have designated Ukrainian media outlets as priority targets. This is a strategic shift. Media has moved up the Russian targeting hierarchy alongside energy and government.

Alex: For CISOs at media companies, broadcast organizations, or even PR and communications firms with clients in contested geopolitical spaces, this is a direct signal. You're not collateral damage. You're the objective. Information warfare is a core component of modern conflict, and the infrastructure that produces and distributes information is a legitimate target in the adversary's calculus.

Jordan: And it extends beyond Ukraine. If you're a Western media organization covering the conflict, covering sanctions, covering anything that intersects with Russian strategic narratives, your risk profile just went up.

Alex: All right, Jordan. Let's talk about the story you opened with. JadePuffer.

Jordan: So researchers have published what they describe as the first fully agentic AI-powered ransomware campaign. JadePuffer uses autonomous AI agents to handle the entire attack chain. Reconnaissance, initial access exploitation, lateral movement, privilege escalation, and encryption. No human operator making real-time decisions.

Alex: Let me be direct about what this means operationally. The thing that has historically given defenders a fighting chance against ransomware is dwell time. The gap between initial compromise and encryption where you can detect anomalous behavior and intervene. Agentic ransomware compresses that window potentially to minutes.

Jordan: And it's adaptive. These agents can make decisions based on what they find in the environment. They're not following a static playbook. They're adjusting. That means your detection logic built around known attack patterns may not trigger until it's too late.

Alex: So the defensive implications are clear. You need to be investing in detection capabilities that operate at machine speed. Behavioral analytics that don't depend on signatures. Automated containment that can isolate compromised segments without waiting for a human to approve the action. And your incident response playbooks need a scenario where encryption starts 20 minutes after initial access, not 20 days.

Jordan: Paired with JadePuffer, there's a related story about SkillCloak, a technique that lets malicious AI agent plugins evade static scanners more than 90 percent of the time using self-extracting packing. As enterprises rush to adopt AI coding agents and their plugin ecosystems, the supply chain for agent skills is effectively unvetted.

Alex: This is the AI supply chain problem we've been warning about. You're adopting tools that accept third-party plugins, and the scanning tools you rely on to catch malicious code are failing against basic evasion. The researchers did build a runtime checker that catches most of these attempts, which is encouraging. But the message for CISOs is clear. Static analysis alone is not sufficient for the AI agent ecosystem. You need runtime behavioral monitoring of what these agent skills actually do when they execute.

Jordan: Let's pivot to something more immediately actionable. Adobe ColdFusion.

Alex: CVE-2026-48282. Maximum severity. Actively exploited in the wild, confirmed by KEVIntel. If you run ColdFusion, and a surprising number of enterprises and government agencies still do, this needs to be patched today. Not this sprint. Today.

Jordan: ColdFusion is one of those platforms that lives in the forgotten corners of enterprise environments. Legacy web apps, internal portals nobody remembers building. If your asset inventory isn't comprehensive, you might not even know you're exposed.

Alex: Which is why this is also an asset management story. If you can't confidently say you've accounted for every ColdFusion instance in your environment, that's a problem that existed before this CVE and will exist after you patch it. Get the inventory right.

Jordan: Last item. A new report from Kaseya shows that guest accounts made up 69 percent of monitored SaaS accounts in 2025, an increase of 1.9 million year over year. These are contractor accounts, partner accounts, vendor accounts that were created for temporary access and never deprovisioned.

Alex: Sixty-nine percent. That number should be shocking, but honestly, it tracks with what I've seen. Every SaaS platform makes it trivially easy to invite a guest and almost none of them make it easy to audit or expire that access. Add in persistent OAuth grants that outlive the business relationship, and you've got orphaned access paths everywhere.

Jordan: And weak MFA on those guest accounts. Many organizations enforce strong MFA for employees but treat guest accounts as low-risk. They're not low-risk. They're high-risk with low visibility.

Alex: The fix here is governance, not technology. You need policies that tie guest account lifecycles to business relationships with automatic expiration. You need regular access reviews that specifically include OAuth grants. And you need to treat guest accounts as the threat surface they actually are.

Jordan: Looking ahead this week, the thread connecting these stories is acceleration. Adversaries are moving faster, whether it's agentic ransomware compressing attack timelines, commercial spyware hitting new categories of targets, or the AI agent supply chain outpacing our ability to secure it. The question for CISOs isn't whether they need to move faster. It's where to invest in automation and where human judgment still matters.

Alex: I'd add that the governance stories are just as urgent as the technical ones. SaaS sprawl, guest account hygiene, AI tool policies. Alibaba banning Claude internally, that's a governance decision that a lot of organizations haven't made yet. The organizations that get ahead of this week are the ones matching their detection speed to the threat's operational speed while also cleaning up the identity sprawl that gives attackers room to maneuver.

Jordan: Prioritize the ColdFusion patch. Audit your SaaS guest accounts. And start war-gaming a ransomware scenario where dwell time is measured in minutes, not weeks.

Alex: That's Cleartext for Monday, July 6th, 2026. Show notes and links to every story we covered are at cleartext.fm. We're back tomorrow. Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-07-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 17 stories across 5 topic areas, including: European Parliament Member Investigating Spyware Was Hacked With Pegasus; North Korean Hackers Publish 108 Malicious Packages and Extensions in PolinRider Campaign; US offers $10 million for info on group behind Signal and WhatsApp hacking spree.

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

Why it matters to CISOs: Citizen Lab's confirmation that the PEGA Committee member overseeing spyware investigations was himself repeatedly targeted with Pegasus underscores that senior executives and board members investigating or regulating sensitive topics are high-value spyware targets — and mobile device security cannot be treated as a consumer problem.

📖 Read full article

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

Why it matters to CISOs: North Korea's Contagious Interview campaign has industrialized software supply chain poisoning across npm, Packagist, Go, and Chrome extensions simultaneously — any organization with developer pipelines pulling from these registries faces live, ongoing exposure that requires immediate dependency auditing.

📖 Read full article

Ars Technica Security · Jun 29 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A $10M State Department bounty signals that Russian state-sponsored targeting of encrypted messaging apps is now an officially designated national security threat — CISOs protecting executives who use Signal or WhatsApp for sensitive communications must treat these platforms as active attack surfaces.

📖 Read full article

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

Why it matters to CISOs: Mustang Panda's use of legitimate SaaS platforms (Zoho WorkDrive) as covert C2 channels in active government compromises is a direct signal to CISOs that blocking known malicious IPs is insufficient — adversary C2 now lives inside trusted cloud services that cannot be blanket-blocked.

📖 Read full article

Infosecurity Magazine · Jul 03 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Ransomware-as-a-Service is reconsolidating around a smaller number of dominant, highly capable operators — Qilin leading — which means organizations face adversaries with more resources, better tooling, and corporate-style negotiation and extortion capabilities.

📖 Read full article

The Hacker News · Jul 02 · Relevance: ██████████ 10/10

Why it matters to CISOs: This is the first documented end-to-end AI-autonomous ransomware attack — from initial exploitation through lateral movement to encryption — eliminating human operators from the kill chain and compressing attack timelines in ways current detection playbooks are not designed to catch.

📖 Read full article

The Hacker News · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: The FortiBleed mass credential-harvesting campaign against thousands of FortiGate firewalls has now been directly attributed to active ransomware deployment pipelines — organizations with unpatched Fortinet perimeter devices face imminent follow-on intrusion risk.

📖 Read full article

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

Why it matters to CISOs: Anubis ransomware affiliates are actively exploiting Citrix Bleed 2 (CVE-2025-5777) alongside BYOVD and supply chain credential abuse, giving CISOs a clear picture of the current initial-access playbook they need to close against.

📖 Read full article

Krebs on Security · Jul 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The FBI's seizure of NetNut — a publicly traded Israeli company's residential proxy service built on a two-million-device botnet — highlights that legitimate-looking commercial proxy services can be built on compromised enterprise and consumer infrastructure used by threat actors to obscure attack origin.

📖 Read full article

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

Why it matters to CISOs: The extradition of a 19-year-old Scattered Spider member from Finland — linked to an $8M ransom demand against a luxury retailer — demonstrates that international law enforcement coordination against English-speaking cybercrime gangs is accelerating, which may deter recruitment but not active operators.

📖 Read full article

The Record (Recorded Future) · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: Max Schrems' announced legal challenge to the EU-US Data Privacy Framework could invalidate transatlantic data transfers for the third time — CISOs and legal teams at multinationals must immediately re-evaluate data flow architectures and vendor contracts for EU-US contingency planning.

📖 Read full article

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

Why it matters to CISOs: DHS's launch of the ANCHOR-CI program to replace the Trump administration's shuttered public-private infrastructure security coordination body represents a partial restoration of threat intelligence sharing for critical infrastructure operators — CISOs in energy, finance, and healthcare should evaluate participation.

📖 Read full article

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

Why it matters to CISOs: The US government's negotiated release of Anthropic's Fable and Mythos models — previously export-controlled due to offensive cyber capabilities — with new classifiers blocking 99%+ of jailbreaks sets a policy template for how dual-use AI models will be governed and released going forward.

📖 Read full article

Cybersecurity Dive · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Bitdefender's finding that a majority of security professionals have been instructed to conceal a breach represents a direct legal and career risk for CISOs navigating SEC disclosure rules and state-level breach notification mandates — the pressure to suppress is real and documented.

📖 Read full article

The Hacker News · Jul 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: DeepSeek was used to generate novel, functional ransomware that runs entirely inside the browser across all major platforms — demonstrating that frontier AI models will lower the barrier for novel malware creation, not just script-kiddie tooling.

📖 Read full article

VentureBeat Security · Jun 29 · Relevance: █████████░ 9/10

Why it matters to CISOs: Agentjacking via developer toolchain integrations is a systemic, enterprise-scale risk: any organization running AI coding agents connected to Sentry, Jira, Datadog, or PagerDuty is exposed to prompt injection that executes attacker code with developer-level privileges, with zero alerts fired.

📖 Read full article

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

Why it matters to CISOs: Active exploitation of a CVSS 8.8 SharePoint RCE via deserialization — added to CISA KEV — means any internet-exposed or internally accessible SharePoint Server must be patched immediately; this class of SharePoint vulnerability has repeatedly led to full domain compromise in enterprise environments.

📖 Read full article

Jordan: The week an AI agent ran a ransomware attack start to finish with no human in the loop. That's not a research paper. That's not a proof of concept at a conference. That happened in production. And if that doesn't reframe how you think about detection timelines and attacker economics heading into Q3, I'm not sure what will.

Alex: Welcome to Cleartext. I'm Alex Chen, alongside Jordan Reeves. This is your Saturday Week in Review for the week ending July 4th, 2026. If you couldn't keep up this week — and honestly, this was one of those weeks where even keeping up full-time felt insufficient — here's what mattered and what it means. We're covering four major themes today. First, AI crossed a line this week, both as a weapon and as an attack surface. Second, the ransomware ecosystem is consolidating and industrializing in ways that should change how you model risk. Third, nation-states are targeting the tools we trust — encrypted messengers, SaaS platforms, developer toolchains. And fourth, governance pressure is building on multiple fronts from data transfers to breach disclosure to export controls on AI itself. Let's get into it.

Jordan: So let's start with AI, because two stories this week together paint a picture that I think the industry hasn't fully absorbed. Sysdig published research on a threat actor they're calling JADEPUFFER. An LLM autonomously exploited a critical RCE in Langflow — CVE-2026-33017, CVSS 9.3 — then moved laterally, stole credentials, found the production database, encrypted it, and wiped backups. No human touched the keyboard at any point. This isn't theoretical. This is documented.

Alex: And the business implication is stark. Our detection playbooks, our SOC workflows, our incident response runbooks — they are built around human attacker behavior. Dwell time assumptions, the pace of lateral movement, the patterns of credential access. When you remove the human from the kill chain, you compress timelines in ways that break those assumptions. If you're a CISO budgeting for MDR or XDR, you need to be asking your vendors right now: what is your detection model for AI-speed intrusions?

Jordan: And then pair that with the second AI story. Researchers demonstrated that DeepSeek generated functional, novel, cross-platform browser ransomware that abuses a legitimate Chromium API. Runs on Windows, Linux, macOS, Android. No OS-level persistence needed. It lives entirely in the browser. The significance isn't that someone made ransomware — it's that a frontier AI model produced a genuinely novel attack technique that a human hadn't published before. It found a real Chromium API and weaponized it.

Alex: So you've got AI generating novel offensive techniques and AI autonomously executing full attack chains. Those are two different capabilities converging. And then on the defensive side, we saw the agentjacking research from Tenet Security. They achieved an 85 percent success rate hijacking AI coding agents — Claude Code, Cursor, Codex — through a single crafted Sentry error event. No authentication required. The agent executes attacker code with full developer privileges. EDR didn't fire. WAF didn't fire. IAM didn't catch it.

Jordan: Sentry acknowledged the flaw is, quote, "technically not defensible." And the exposure extends to Datadog, PagerDuty, Jira — any integration feeding data into AI coding agents. The Cloud Security Alliance classified this as a systemic MCP vulnerability class. If your engineering teams are using AI coding assistants connected to these platforms, you have an open channel from the internet to code execution with developer privileges. That's not a hypothetical risk. That's architecture.

Alex: The through-line here is that AI is simultaneously lowering the barrier for attackers and creating entirely new attack surfaces in our own toolchains. This is the week that became undeniable.

Jordan: Let's shift to ransomware, because the landscape moved this week in ways that matter structurally. Qilin has emerged as the dominant ransomware-as-a-service operation. Infosecurity Magazine reported on the consolidation trend — after law enforcement disrupted LockBit and others, the ecosystem didn't fragment into a hundred small groups. It reconsolidated around fewer, better-resourced platforms. Qilin is running corporate-style operations with negotiation infrastructure, affiliate management, the works.

Alex: And the FBI issued concurrent warnings about partnerships like TeamPCP that are enabling what they called industrialized attack scale. This is important for how CISOs model the threat. You're not facing a fragmented landscape of opportunistic criminals anymore. You're facing well-resourced platforms with the operational maturity of a mid-size SaaS company.

Jordan: The initial access picture came into sharp focus too. FortiBleed — the mass credential-harvesting campaign against FortiGate firewalls — was directly linked to INC and Lynx ransomware operations. Researchers found operators tied to FortiBleed infrastructure actively working negotiation panels for both groups. So the pipeline is clear: exploit perimeter device, harvest credentials, hand off to ransomware operator. And they're chaining this with a suspected Nextcloud zero-day to broaden access.

Alex: Simultaneously, Anubis ransomware affiliates are exploiting Citrix Bleed 2 — CVE-2025-5777 — alongside bring-your-own-vulnerable-driver techniques and supply chain credential abuse. The current initial access playbook is diversified and multi-vector. If you're relying on a single control — just patching, just EDR, just network segmentation — you're going to lose. The adversary is designed to route around any single defense.

Jordan: And CISA added the SharePoint RCE, CVE-2026-45659, to the Known Exploited Vulnerabilities catalog. CVSS 8.8, deserialization flaw, patched back in May. If you haven't patched SharePoint in six weeks, you've been exposed to active exploitation for at least part of that window. This class of SharePoint vulnerability has been the entry point for full domain compromise repeatedly.

Alex: The message on ransomware this week is consolidation plus diversified access equals elevated risk. Your perimeter devices — Fortinet, Citrix, SharePoint — are the front door. Patch velocity isn't optional anymore.

Jordan: Now, nation-states. This was a big week. Let's start with the Pegasus story because it's symbolically important. Citizen Lab confirmed that Stelios Kouloglou, a European Parliament member who sat on the PEGA Committee — the committee literally investigating spyware abuse — was himself repeatedly hacked with Pegasus while conducting that investigation.

Alex: The irony is obvious. But for CISOs, the lesson is concrete. If you have board members, executives, or senior leaders who are involved in regulatory oversight, investigations, or geopolitically sensitive business, they are high-value targets for commercial spyware. Mobile device security for these individuals cannot be treated as a consumer problem. You need managed device policies, lockdown mode, regular forensic checks. This is an executive protection issue now.

Jordan: The State Department put a $10 million bounty on two Russian state-linked groups targeting Signal and WhatsApp accounts of political, defense, and intelligence-adjacent targets. That bounty level — that's the same tier as rewards for information on major terrorist organizations. It tells you how seriously the US government views the compromise of encrypted messaging. For CISOs, if your executives are using Signal for sensitive communications, which many are, those platforms are now confirmed active attack surfaces for state-sponsored operations.

Alex: And on the Chinese side, Mustang Panda is actively compromising Indian government networks using Zoho WorkDrive as a command-and-control channel. This is the SaaS C2 problem. The adversary's command traffic is flowing through legitimate cloud services that you can't blanket-block without breaking business operations. Your DLP and your proxy logs won't flag traffic to Zoho as suspicious because half your workforce probably uses Zoho legitimately.

Jordan: North Korea rounded out the nation-state picture with the PolinRider campaign — 108 malicious packages and browser extensions published across npm, Packagist, Go, and Chrome simultaneously. And critically, they're not just creating new packages. They're compromising legitimate maintainer accounts and pushing malware through trusted, existing packages. If your developers pulled dependencies this week without verification, you may already have exposure.

Alex: The common thread across all four nation-state stories is that adversaries are operating inside trusted channels — legitimate SaaS, legitimate package registries, legitimate messaging apps. The perimeter-based mental model is thoroughly broken.

Jordan: Governance. Two stories that deserve CISO attention heading into the back half of the year. Max Schrems announced a formal legal challenge to the EU-US Data Privacy Framework, triggered by a recent Supreme Court decision he argues undermines the DPF's legal foundation. If successful, this would be the third invalidation of a transatlantic data transfer mechanism.

Alex: If you're a multinational, you've been through Safe Harbor and Privacy Shield. You know the drill. But the operational disruption of a third invalidation would be enormous. Data flow architectures, vendor contracts, cloud deployments — all of it potentially needs restructuring. Legal and security teams should be running contingency scenarios now, not waiting for a ruling.

Jordan: And Bitdefender published survey data showing that a majority of cybersecurity professionals have been told at some point to conceal a breach. In the context of SEC disclosure rules and state notification mandates that create personal liability for CISOs, this is career-ending and potentially criminal territory. The pressure to suppress is real. The data now confirms it's widespread.

Alex: If you're a CISO and you receive that instruction, document it. Get it in writing. Consult outside counsel immediately. The regulatory environment has shifted. The personal liability exposure is real. This is not a risk you absorb for the organization.

Jordan: Two quick additional governance notes. DHS launched the ANCHOR-CI program to replace public-private critical infrastructure coordination that was eliminated in 2025. If you're in energy, finance, or healthcare, evaluate participation. And the Commerce Department lifted export controls on Anthropic's Fable and Mythos cybersecurity AI models after Anthropic implemented classifiers blocking 99 percent of jailbreaks. That sets a precedent for how dual-use AI models will be governed — conditional release with technical guardrails. Expect that template to be applied broadly.

Alex: And one law enforcement win worth noting. The FBI seized NetNut, a residential proxy service operated by NASDAQ-listed Alarum Technologies, built on a two-million-device botnet. A publicly traded company's commercial service, running on compromised infrastructure. And a 19-year-old Scattered Spider member was extradited from Finland to face charges. International coordination against English-speaking cybercrime groups is clearly accelerating.

Jordan: So stepping back — what defined this week?

Alex: This was the week AI became operationally real on both sides of the fight. Not as a buzzword, not as a future concern. An AI agent ran a ransomware attack autonomously. An AI model generated a novel attack technique. And AI coding assistants were hijacked through legitimate developer toolchains. If your 2026 strategy doesn't have AI threat modeling as a first-class workstream, you are behind.

Jordan: And underneath that, the fundamentals remain brutal. Ransomware is consolidating, not fragmenting. Nation-states are operating inside your trusted services. Your perimeter devices are under active exploitation. The governance landscape is shifting under your feet. Next week, I'd expect follow-on activity from PolinRider and FortiBleed. Patch SharePoint and Citrix if you haven't. And have a serious conversation with your engineering leadership about AI agent security in developer workflows.

Alex: That's the week. The daily show returns Monday. Show notes and links to every story we covered are at cleartext.fm. Have a safe Fourth of July weekend, and we'll see you next week.

Jordan: Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-07-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 5 topic areas, including: Someone infected a spyware probe overseer with spyware; FBI Seizes NetNut Proxy Platform, Popa Botnet; Alleged longstanding member of Scattered Spider extradited to US.

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

Why it matters to CISOs: Citizen Lab's confirmation that a sitting EU lawmaker investigating commercial spyware was repeatedly targeted with Pegasus underscores the political weaponization of enterprise-grade surveillance tools and should inform executive and board mobile device security policies.

📖 Read full article

Krebs on Security · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The FBI's seizure of a two-million-device botnet operated through a publicly traded Israeli company illustrates how commercial proxy services can serve as threat actor infrastructure, with implications for enterprise threat intelligence and vendor due diligence.

📖 Read full article

CyberScoop · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The extradition of a key Scattered Spider member signals continued law enforcement pressure on the group responsible for high-profile enterprise breaches, and reinforces the need for CISOs to maintain social engineering and SIM-swapping defenses even as the group's operational tempo may be disrupted.

📖 Read full article

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

Why it matters to CISOs: A breach of a DHS intelligence-sharing network with potential national security implications signals ongoing vulnerability in federal cyber infrastructure, raising questions about third-party data sharing risks and supply chain exposure for enterprise partners.

📖 Read full article

The Record (Recorded Future) · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: A legal challenge to the EU-US Data Privacy Framework could invalidate the primary mechanism enterprises rely on to transfer personal data across the Atlantic, forcing CISOs to urgently revisit data residency architectures and Standard Contractual Clauses as fallback.

📖 Read full article

Cybersecurity Dive · Jul 02 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Evidence that security professionals are routinely pressured to conceal breaches creates direct personal legal liability for CISOs under SEC and other disclosure frameworks, and signals a governance gap that boards need to address urgently.

📖 Read full article

The Record (Recorded Future) · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The delay of the UK's National Cyber Action Plan creates near-term regulatory uncertainty for enterprises operating in the UK market and signals that strategic cyber policy commitments may slip further as political instability continues.

📖 Read full article

Dark Reading · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: Threat actors who compromised thousands of Fortinet firewalls via FortiBleed are now monetizing that access through ransomware partnerships, and are also exploiting a Nextcloud zero-day—making this an active, escalating threat to enterprise perimeter infrastructure.

📖 Read full article

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

Why it matters to CISOs: Active exploitation of Citrix Bleed 2 (CVE-2025-5777) by the Anubis ransomware group for initial access, combined with BYOVD and supply chain credential abuse, represents an immediate threat to enterprises running Citrix NetScaler environments.

📖 Read full article

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

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

Alex: We have a packed show today. The EU-US data transfer framework is under threat again, courtesy of Max Schrems. We've got a major DHS intelligence network breach, active ransomware campaigns exploiting Fortinet and Citrix infrastructure, the FBI taking down a two-million-device botnet run through a Nasdaq-listed company, a Scattered Spider extradition, a damning survey on breach concealment, and a story that honestly reads like satire but isn't — a European lawmaker investigating spyware got hit with spyware. Jordan, take us there.

Jordan: Yeah, let's start with the Pegasus story because it's one of those things that sounds like a movie pitch but is very real. Citizen Lab has forensically confirmed that Stelios Kouloglou, who is a sitting member of the European Parliament and specifically a member of the PEGA Committee — the committee created to investigate commercial spyware abuses — had his device infected with NSO Group's Pegasus. Not once. Twice. The audacity is almost artistic.

Alex: It would be funny if it weren't so alarming. And for our audience, the reason this matters beyond the geopolitical theater is what it tells you about the threat model for anyone in an oversight or governance role. If a sitting EU lawmaker investigating spyware isn't safe, your general counsel, your board members, your executives traveling internationally — they're absolutely viable targets for commercial surveillance tools.

Jordan: Exactly. And this isn't some hypothetical. NSO Group markets Pegasus as a law enforcement tool, but the client list has always been the problem. We're talking about nation-state customers who will deploy this against political targets, journalists, activists, and yes, corporate executives. If your C-suite is operating on the assumption that their iPhone is secure because they have MDM enrolled, that assumption needs to be revisited. Pegasus exploits are zero-click. They don't require the target to do anything.

Alex: So the action item here is straightforward. If you haven't already deployed Lockdown Mode on executive devices, that conversation needs to happen Monday. And beyond that, this should inform your executive device refresh cadence, your travel security protocols, and honestly, your board reporting on surveillance risk. This isn't a fringe concern anymore.

Jordan: Let's pivot to the DHS breach, because this one has real gravity. A senior Democrat on the Senate Intelligence Committee confirmed that a Homeland Security intelligence-sharing network was compromised, and explicitly warned that the accessed information may risk national security.

Alex: The details are still emerging, but the pattern is what matters. This is another in a long sequence of US government network compromises. And for CISOs in the private sector, the question you need to be asking is: what data did we share through federal information-sharing programs, and does this breach create exposure for us? If your organization participates in any DHS CISA information-sharing frameworks, you need to be talking to your government affairs team and your legal counsel about what was in that pipeline.

Jordan: And I'll add that this also affects trust in the broader information-sharing ecosystem. Every time a government network gets popped, it makes the next CISO more reluctant to share threat intelligence through official channels. That's a compounding problem for the entire community.

Alex: Now let's connect two stories that are really one story. FortiBleed and Citrix Bleed 2. Jordan, walk us through the threat landscape here.

Jordan: So these are two separate vulnerability exploitation campaigns, but they share a common operational model that's worth understanding together. FortiBleed — the actors who compromised thousands of Fortinet firewalls — they've now moved from persistent access to monetization. They're partnering with INC and Lynx ransomware operations to convert those footholds into extortion revenue. And they're stacking on a suspected Nextcloud zero-day to expand their access within compromised environments.

Alex: So if you're running Fortinet perimeter infrastructure, this is no longer a "patch and monitor" situation. This is an "assume compromise and hunt" situation.

Jordan: Correct. And simultaneously, the Anubis ransomware group is actively exploiting CVE-2025-5777, which is Citrix Bleed 2, to get initial access into enterprise environments running NetScaler. The attack chains are sophisticated — BYOVD techniques, legitimate RMM tooling for lateral movement, and supply chain credential theft to broaden the blast radius. This is not smash-and-grab. These are methodical, multi-stage intrusions.

Alex: The action items are clear. For Fortinet shops, assume compromise on unpatched devices and run threat hunts now. For Citrix NetScaler environments, patch CVE-2025-5777 immediately if you haven't, audit your RMM tooling for unauthorized instances, and review your supply chain credential hygiene. Both of these represent active, escalating threats, not theoretical risk.

Jordan: Let's shift to the FBI's takedown of NetNut and the Popa botnet. This one is fascinating because of who was behind it. NetNut is a residential proxy service operated by Alarum Technologies, which is a publicly traded company on the Nasdaq. The FBI seized hundreds of domains after investigations connected NetNut to a botnet of at least two million compromised devices.

Alex: This is a vendor due diligence story. A Nasdaq-listed company was operating infrastructure that served as a platform for threat actors. The residential proxy market has always been murky, but this is a clear example of how commercial services that look legitimate on paper can be deeply intertwined with criminal infrastructure.

Jordan: And for CISOs, the question is twofold. First, is any of your traffic routing through residential proxy networks that you don't fully understand? And second, are your threat intelligence feeds and your fraud detection systems calibrated to detect traffic originating from residential proxy infrastructure? Because that's how attackers look like legitimate users.

Alex: Good. Let's talk about Scattered Spider. Peter Stokes, alleged to be a longstanding member, has been extradited to the US to face federal charges. Jordan, is this meaningful or is this another arrest that doesn't change the operational picture?

Jordan: It's meaningful in the aggregate but not decisive. Scattered Spider is a loosely organized group. Taking one member off the board disrupts but doesn't dismantle. That said, the law enforcement pressure is cumulative. Multiple arrests, multiple countries cooperating — it raises the cost and the risk for these operators. The eight-million-dollar ransom demand against the luxury retailer and the two million in losses even without payment — that's the kind of case that makes prosecutors enthusiastic.

Alex: And for CISOs, the reminder is that Scattered Spider's playbook hasn't changed. They target help desks with social engineering. They use SIM swapping. These are people problems, not technology problems. If your help desk verification procedures haven't been hardened against these specific techniques, the arrest of one member doesn't reduce your risk.

Jordan: Now, the governance stories. Alex, the Data Privacy Framework challenge is potentially enormous.

Alex: It really is. Max Schrems and noyb have formally notified European officials that they plan to sue to invalidate the EU-US Data Privacy Framework. If you've been in this space for more than five minutes, you've seen this movie before. Safe Harbor was invalidated. Privacy Shield was invalidated. DPF was supposed to be the durable replacement, and now it's under legal challenge following the Supreme Court decision that changed the underlying US legal landscape.

Jordan: And the trajectory is predictable. Even if the challenge takes a year or two to wind through the courts, the uncertainty itself is a problem. If you're a CISO at a company that transfers EU personal data to the US, and your legal basis is DPF, you need a fallback architecture. Standard Contractual Clauses, data residency, whatever your legal team recommends — but you can't be caught flat-footed.

Alex: Exactly. Start the conversation with your DPO and your privacy counsel now. Map your transatlantic data flows. Understand where your SCCs are current and where they're not. This isn't a fire drill yet, but it's a fire watch.

Jordan: And then there's the Bitdefender survey. A majority of cybersecurity professionals say they've been instructed to conceal a breach from regulators or the public.

Alex: This is a governance crisis, full stop. Under SEC rules, under GDPR, under virtually every modern regulatory framework, concealing a material breach creates personal criminal and civil liability. For CISOs specifically, we've seen the SolarWinds case, we've seen the Uber case. The message from regulators is unambiguous: if you know about a material breach and you help conceal it, you are personally at risk.

Jordan: And the survey finding that US companies are simultaneously more confident in their defenses and more strained operationally — that's cognitive dissonance that boards need to understand. Confidence without capacity is how you get pressure to hide bad news.

Alex: If you're a CISO and you're being pressured to conceal, document everything, engage outside counsel, and understand your whistleblower protections. And if you're a board member listening to this, create the reporting structures that make concealment unnecessary. This is a culture problem, not a security problem.

Jordan: Last note — the UK's National Cyber Action Plan has been delayed due to the Labour leadership crisis. It was supposed to publish Monday.

Alex: For anyone operating in the UK market, this creates near-term regulatory uncertainty. We don't know how long the delay will be. The leadership contest opens July 9th, and depending on how that plays out, strategic cyber policy could slip significantly. Monitor it, but don't pause your compliance planning.

Jordan: So stepping back, Alex — what's the thread this week?

Alex: The thread is that the structures we rely on are fragile. The EU-US data transfer framework, government intelligence-sharing networks, the assumption that oversight bodies are safe from surveillance, the expectation that breaches will be honestly reported. All of those are under stress simultaneously. The CISO's job right now is to build resilience that doesn't depend on any single structure holding.

Jordan: And on the technical side, the perimeter is on fire. Fortinet, Citrix, residential proxies as threat infrastructure — the attackers are monetizing access faster than most organizations are patching. If you take one action this weekend, run a threat hunt against your edge infrastructure. Don't wait for Monday.

Alex: That's our show for today. Show notes and links to every story we covered are at cleartext.fm. Have a safe Fourth of July weekend. We'll be back Monday.

Jordan: Stay sharp.

Cleartext is an automated daily podcast for CISOs and security leaders. Generated 2026-07-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 10 stories across 4 topic areas, including: US lifts export controls on Anthropic’s frontier cybersecurity AI models; Srsly Risky Biz: America won't beat the distillation ecosystem; AI Agent Exploits Langflow RCE to Automate Database Ransomware Attack.

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

Why it matters to CISOs: The US government's decision to lift export controls on Anthropic's frontier cybersecurity AI models—with new guardrails—reshapes the global AI security landscape and raises questions about adversary access to powerful offensive and defensive AI capabilities.

📖 Read full article

Risky Business News · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Chinese AI labs exploiting a grey market for US model access logs to conduct distillation attacks represents a structural intelligence threat that could erode the US's AI security edge—directly relevant to CISOs evaluating AI supply chain risk and model provenance.

📖 Read full article

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

Why it matters to CISOs: This marks a strategic inflection point: an LLM-driven agent autonomously executed a full ransomware attack chain from initial access through encryption, signaling that AI-accelerated attacks will compress defender response windows and stress-test current detection and response architectures.

📖 Read full article

BleepingComputer · Jul 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: An 81-million-attempt password-spraying campaign against Microsoft 365 over just two weeks underscores the industrial scale of credential attacks on enterprise identity infrastructure, making this an urgent prompt to review MFA enforcement, conditional access policies, and legacy authentication blocking.

📖 Read full article

BleepingComputer · Jul 01 · Relevance: █████████░ 9/10

Why it matters to CISOs: The Homeland Security Information Network is a sensitive government-private sector intelligence-sharing platform; its compromise potentially exposes threat intelligence shared by enterprise partners and signals attackers may have visibility into federal-private security coordination.

📖 Read full article

The Hacker News · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: Mass FortiGate credential theft is now directly tied to active ransomware deployment pipelines, meaning organizations with exposed Fortinet infrastructure face imminent ransomware risk and should treat stolen credentials as already weaponized.

📖 Read full article

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

Why it matters to CISOs: A cluster of simultaneous breach disclosures across major Japanese multinationals—spanning insurance, consumer goods, manufacturing, and telecom—suggests coordinated or opportunistic targeting of Japanese enterprise infrastructure with potential supply chain and partner notification implications for global organizations.

📖 Read full article

BleepingComputer · Jul 02 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: ShinyHunters' breach of a major medical device manufacturer highlights persistent third-party and cloud storage risk in healthcare; CISOs in regulated industries should review vendor access controls and assess exposure through shared cloud environments this threat actor has repeatedly targeted.

📖 Read full article

The Hacker News · Jul 02 · Relevance: █████████░ 9/10

Why it matters to CISOs: A high-severity RCE vulnerability in Microsoft SharePoint Server is now confirmed actively exploited and added to CISA's KEV catalog, requiring immediate remediation given SharePoint's near-universal deployment in enterprise environments as a document collaboration and intranet platform.

📖 Read full article

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

Why it matters to CISOs: With over 900 Oracle EBS instances exposed and under active attack, enterprises running Oracle Payments and related EBS modules face immediate financial system compromise risk, warranting emergency inventory and remediation checks.

📖 Read full article

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

Jordan: And I'm Jordan Reeves. So, Sysdig just published research on what they're calling the first documented ransomware attack run end-to-end by an AI agent. No human operator in the loop. The LLM handled initial access, credential theft, lateral movement, encryption, and data wiping. All of it. Autonomously. We've been warning about this inflection point for two years, and now we're here.

Alex: Yeah, we're going to dig into that. We've also got the US lifting export controls on Anthropic's frontier cybersecurity AI models, a confirmed breach of DHS's intelligence-sharing platform, a SharePoint RCE that just hit CISA's KEV catalog, and FortiBleed credentials now directly linked to active ransomware pipelines. Plus a massive password-spraying campaign hitting Microsoft 365 at industrial scale. Lot to cover. Let's get into it.

Jordan: Let's start with the AI stories because they're all connected. The Commerce Department reached an agreement with Anthropic to lift export controls on their Mythos and Fable models, the frontier cybersecurity AI systems. There are new guardrails and classifiers as part of the deal, but the fundamental shift here is that these models are now going to be available to allied nations and potentially beyond.

Alex: And this is the core tension that US policymakers have been wrestling with for over a year. You maintain AI dominance by getting your models deployed everywhere, adopted everywhere, embedded in allied security architectures. But the moment you loosen the reins, you lose some control over who ultimately gets access to the capabilities. It's a classic dual-use problem, except the speed of proliferation with software is fundamentally different from hardware export controls.

Jordan: Which connects directly to the Risky Business reporting on Chinese AI labs running distillation attacks against US models. The mechanism is clever and frankly hard to counter. Chinese consumers buy legitimate access to US models through resellers. The logs of those interactions, the request-response pairs, become training data for distillation. Chinese labs may actually be subsidizing this grey market specifically to harvest those logs at scale.

Alex: So for CISOs, there are two things to think about here. First, model provenance. If you're deploying AI security tools, you need to understand where the underlying model came from and whether it's been influenced by distilled capabilities from frontier models that were supposed to be controlled. Second, if your organization is using any of these models in sensitive contexts, the logs of your interactions could be feeding adversary training pipelines through channels you have zero visibility into.

Jordan: Right. The supply chain risk here isn't the traditional one. It's not a compromised library or a backdoored update. It's the intellectual output of your interactions with AI models becoming a training input for adversary systems. That's a novel category of data leakage that most security programs aren't structured to detect or prevent.

Alex: Let's pivot to the JADEPUFFER story because this is genuinely significant. Sysdig's threat research team documented a threat actor using an LLM-driven agent to execute a full ransomware kill chain against a production database. The initial access was through the Langflow RCE vulnerability, and from there the agent handled everything autonomously.

Jordan: What makes this different from the AI-assisted attacks we've seen before is the absence of human decision-making in the loop. Previous cases involved operators using AI to write better phishing emails or generate exploit code, essentially AI as a productivity tool for attackers. This is AI as the operator. The implications for defenders are significant because the attack tempo changes fundamentally.

Alex: That's the board-level conversation. When your adversary's attack chain is fully automated and can execute in minutes rather than hours or days, your detection and response windows compress dramatically. The mean time to respond that you've been reporting to your board may no longer be fast enough. And the economics shift too. The marginal cost of launching an additional attack drops toward zero.

Jordan: CISOs should be asking their SOC leaders a very specific question right now: if an attack progresses from initial access to data encryption in under fifteen minutes with no human pauses for reconnaissance or decision-making, does our detection and response architecture actually catch it in time? For most organizations, the honest answer is no.

Alex: Let's move to the DHS breach. The Homeland Security Information Network, HSIN, has been confirmed compromised. This is the platform that federal, state, local, and private-sector partners use to share sensitive security information.

Jordan: This is the kind of breach that has second-order effects that are hard to scope. HSIN is where threat intelligence gets shared between government and critical infrastructure operators. If an adversary has visibility into what defenders know, what indicators they're tracking, what coordination is happening, that's an intelligence advantage that undermines the entire collective defense model. It's not just about data exposure. It's about the attacker understanding the defender's playbook.

Alex: If your organization participates in any government information-sharing program, and many critical infrastructure companies do, you should be reviewing what you've shared through those channels and assessing whether that information could be weaponized against your own defenses. Also worth considering whether intelligence you received through HSIN may have been manipulated or whether the breach timeline overlaps with any anomalies in your own environment.

Jordan: Now let's talk about the two vulnerability stories because they both demand immediate action. CVE-2026-45659, the SharePoint Server RCE, just hit CISA's KEV catalog. CVSS 8.8, deserialization of untrusted data, confirmed active exploitation. The patch has been available since May.

Alex: If you haven't patched SharePoint since May, you are actively being targeted. There's no ambiguity here. SharePoint is in virtually every enterprise environment. It holds sensitive documents, it's integrated with Active Directory, it's often internet-facing or accessible through VPN. This is a priority-one remediation item for today, not next week's change window.

Jordan: And separately, over 900 Oracle E-Business Suite instances are exposed to the internet and under active attack. The critical flaw could let attackers compromise Oracle Payments. If you're running EBS, particularly the Payments module, you need an emergency inventory of what's exposed and whether patches have been applied. Financial system compromise is the kind of thing that gets people fired and companies sued.

Alex: Let's connect FortiBleed into this conversation because it illustrates how vulnerability exploitation feeds directly into the ransomware economy. The FortiBleed credential theft campaign is now directly attributed to operators running both INC and Lynx ransomware operations. An operator tied to FortiBleed infrastructure was found actively working negotiation panels for both groups.

Jordan: So the pipeline is: mass exploit FortiGate devices, harvest credentials, stage them for follow-on intrusions, deploy ransomware. If your organization has any Fortinet infrastructure that was exposed during the FortiBleed campaign window, you should treat those credentials as compromised and already in the hands of ransomware operators. Not potentially compromised. Compromised. Rotate everything. Hunt for persistence.

Alex: And speaking of credential attacks at scale, the Microsoft 365 password-spraying campaign is worth flagging. Eighty-one million login attempts over two weeks against enterprise M365 environments. The volume and distribution suggest botnet-driven infrastructure specifically designed to stay under per-IP rate-limiting thresholds.

Jordan: This is a good reminder that MFA is necessary but not sufficient. Legacy authentication protocols that don't support MFA are the soft underbelly here. Conditional access policies need to block legacy auth completely. And if you're not monitoring for distributed, low-and-slow credential attacks across your identity infrastructure, you're likely not seeing this kind of campaign until after they've found a valid credential pair.

Alex: Two more items to cover quickly. Four major Japanese companies, Aflac's Tokyo unit, Sapporo, Nidec, and KDDI, all disclosed breaches simultaneously. Spanning insurance, consumer goods, manufacturing, and telecom. Whether this is coordinated targeting or coincidental timing, if you have Japanese subsidiaries or supply chain relationships with these companies, review your exposure and your notification obligations under both Japanese and your home jurisdiction's regulations.

Jordan: And Medtronic is notifying customers of a ShinyHunters breach. ShinyHunters continues to be prolific in targeting cloud storage environments. For CISOs in healthcare and regulated industries, this is another data point reinforcing that your third-party risk management program needs specific focus on cloud storage configurations and vendor access controls. ShinyHunters has a playbook, and it keeps working.

Alex: So Jordan, stepping back from today's stories, what's the emerging theme you're watching?

Jordan: The theme is compression. Attack timelines are compressing because of AI automation. The window between vulnerability disclosure and active exploitation is compressing. The pipeline from credential theft to ransomware deployment is compressing. And the geopolitical competition around AI capabilities is compressing the timeline for adversaries to match our frontier model capabilities. Every one of these trends pressures the same thing: the defender's decision cycle.

Alex: And that has direct implications for how we structure our security programs. The traditional model of weekly patch cycles, quarterly risk reviews, annual tabletop exercises, those cadences were designed for a threat landscape that moved slower than this one. I'm not saying abandon structure, but CISOs need to be honest with their boards about whether their operational tempo matches the threat tempo. Because right now, for a lot of organizations, it doesn't.

Jordan: The AI agent ransomware story is a signal, not an anomaly. The next twelve months are going to produce more of these. And the organizations that survive them will be the ones that invested in detection and response architectures that don't depend on the attacker being slow.

Alex: That's a good place to leave it. That's Cleartext for Thursday, July 2nd, 2026. Show notes and links to every story we covered are at cleartext.fm. We're back tomorrow.

Jordan: See you then.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 5 topic areas, including: Risky Bulletin: Researcher drops giant cache of zero-days; U.S. lifting export control restrictions on Anthropic’s Mythos, Fable; Microsoft Accelerates Post-Quantum Cryptography Shift to 2029.

Risky Business News · Jul 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A public dump of a large zero-day cache combined with a confirmed DHS network breach and a Supreme Court ruling restricting geofence warrants in the same news cycle represents compounding risk across technical, legal, and governmental dimensions that senior security leaders must track simultaneously.

📖 Read full article

CyberScoop · Jul 01 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: The government's decision to lift export controls on frontier cybersecurity AI models — conditioned on new technical guardrails — sets a precedent for how dual-use AI capabilities will be regulated globally, with direct implications for CISOs evaluating AI security tool procurement, vendor risk, and adversarial AI threat modeling.

📖 Read full article

The Hacker News · Jul 01 · Relevance: ████████░░ 8/10

Why it matters to CISOs: Microsoft's accelerated 2029 deadline for quantum-safe cryptography across Azure compresses the planning window for enterprise security programs that depend on Microsoft infrastructure, forcing CISOs to accelerate their own PQC transition roadmaps and vendor dependency reviews.

📖 Read full article

Infosecurity Magazine · Jun 30 · Relevance: ████████░░ 8/10

Why it matters to CISOs: The Oracle PeopleSoft zero-day campaign is now confirmed to have claimed a major global manufacturer's employee data, expanding the known victim list and underscoring urgency for any enterprise running PeopleSoft HR systems to verify patch status and investigate potential prior compromise.

📖 Read full article

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

Why it matters to CISOs: A simultaneous wave of disclosures across major Japanese enterprises — spanning insurance, consumer goods, manufacturing, and telecom — signals either a coordinated campaign or a common vulnerability in the supply chain; CISOs with Japanese subsidiaries, partners, or vendors should assess exposure immediately.

📖 Read full article

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

Why it matters to CISOs: This directly affects how enterprise security leaders in critical infrastructure sectors receive threat intelligence and coordinate with the federal government — a channel that was severed for over a year. CISOs should evaluate whether their organizations qualify for and should engage with the new ANCHOR-CI framework.

📖 Read full article

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

Why it matters to CISOs: CISA's capacity to support enterprise security programs, issue advisories, and respond to national incidents hinges on staffing levels; a potential reversal of deep cuts would meaningfully affect the agency's operational value to CISOs who rely on it as a resource and partner.

📖 Read full article

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

Why it matters to CISOs: Oracle E-Business Suite is mission-critical ERP for many large enterprises; active at-scale exploitation of a critical flaw with 900+ exposed instances means CISOs must treat this as an emergency patching and exposure-verification priority, not a routine patch cycle item.

📖 Read full article

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

Why it matters to CISOs: A massive automated password spray campaign specifically targeting Azure CLI — a privileged management interface — represents a direct threat to enterprise cloud control planes; CISOs should verify MFA enforcement on all Azure CLI and DevOps pipeline service accounts and review anomalous IPv6 authentication attempts.

📖 Read full article

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

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

Alex: We have a packed show today. An anonymous researcher just dumped a massive cache of zero-days into the wild, and that's landing in the same week as a confirmed DHS network breach and Oracle systems getting hammered across the globe. We'll cover Microsoft compressing the post-quantum timeline to 2029, the U.S. lifting export controls on Anthropic's frontier AI models, a wave of breaches hitting Japanese enterprises, and DHS trying to rebuild the public-private information sharing apparatus it tore down a year ago. Plus, CISA might actually get some of its people back. There's a lot to unpack, so let's move.

Jordan: So let's start with the zero-day dump, because this is the story that should have every SOC on high alert this morning. An anonymous researcher — and I'm using that term loosely — publicly released a large cache of zero-day exploits. We don't have a full accounting yet of what's in there, but the early analysis suggests this covers multiple major platforms. The window between public release and vendor patches is where the damage happens, and that window is now open.

Alex: And the timing here is terrible, or maybe deliberate, depending on how conspiratorial you want to get. This drops in the same cycle as confirmation that a DHS network was breached. Not a contractor. Not a peripheral system. A sensitive DHS network. When the agency responsible for coordinating national cybersecurity defense gets compromised, that's not just an incident — it's a credibility event.

Jordan: Right. And look, DHS has had security issues before, but the optics of this landing alongside a zero-day dump — it raises a question that boards are going to ask: if the government can't secure itself, what does that mean for the threat intelligence and guidance we're receiving from them? And that connects directly to the ANCHOR-CI story we'll get to in a minute.

Alex: There's a third piece in this Risky Business bulletin that CISOs need to track. The Supreme Court issued a ruling restricting geofence warrants. Now, on the surface that's a privacy win, but it has real implications for corporate incident response. If you're dealing with a breach that involves law enforcement, the tools available to investigators just changed. Your legal team needs to understand what this means for evidence collection, legal holds, and how you cooperate with federal investigations going forward.

Jordan: Three simultaneous shifts — technical, institutional, and legal. That's the kind of compounding risk that doesn't show up in any single dashboard.

Alex: Let's stay on the Oracle thread, because this is becoming a campaign, not an isolated incident. Nissan confirmed that employee data was stolen through an Oracle PeopleSoft zero-day. This is the same vulnerability chain that's been hitting enterprises across multiple industries. And separately, BleepingComputer is reporting over 900 Oracle E-Business Suite instances are publicly exposed and under active exploitation right now.

Jordan: Two different Oracle product lines, both under active attack. PeopleSoft is your HR backbone — employee PII, compensation data, banking details. E-Business Suite is your ERP — finance, supply chain, procurement. If you're running either of these, this is not a patch-cycle conversation. This is a drop-everything conversation. Nine hundred exposed EBS instances means there are organizations that don't even know they're internet-facing with critical Oracle infrastructure.

Alex: And the Nissan disclosure is instructive here. This is a global manufacturer with a mature security program, and they still got hit. The PeopleSoft zero-day campaign has now claimed victims across multiple industries. If you're a CISO running PeopleSoft for HR, you need to assume you were targeted and investigate accordingly. Don't wait for the vendor advisory to tell you what you should already be looking for.

Jordan: The downstream risk from HR system compromise is significant. You're not just talking about notification obligations. You're talking about identity fraud, targeted social engineering against your own employees using real compensation and organizational data. That's a gift to any threat actor running a business email compromise operation.

Alex: Let's pivot to the Azure CLI password spray campaign, because this connects to the broader theme of cloud control plane security. Huntress identified over 81 million password spray attempts targeting Azure CLI accounts over a two-week window in June. At least 78 accounts were compromised.

Jordan: Eighty-one million attempts. And the interesting technical detail here is this is coming from an IPv6 range, which a lot of detection stacks still don't monitor with the same rigor as IPv4. The source is an infrastructure provider called LSHIY LLC. This is fully automated, it's ongoing, and it's targeting a privileged management interface. Azure CLI is how your DevOps teams manage cloud infrastructure. A compromised CLI account is essentially root access to your cloud environment.

Alex: The action item is straightforward but urgent. Verify MFA enforcement on every Azure CLI account and every service account in your DevOps pipelines. Review authentication logs specifically for IPv6 anomalies. And if you're using Huntress, they've published indicators. If you're not, go find them anyway.

Jordan: And honestly, if you haven't audited your service account authentication policies in the last 90 days, this is your reason.

Alex: Let's talk about the wave of breaches coming out of Japan. Aflac Japan, Sapporo Holdings, Nidec, and KDDI have all disclosed data breaches in close proximity. These are companies spanning insurance, consumer goods, manufacturing, and telecom. Aflac alone confirmed that policy details, personal information, and banking data were compromised, affecting millions of customers.

Jordan: The clustering is what makes this interesting. Four major companies, four completely different sectors, all disclosing within essentially the same window. That pattern usually points to one of two things: either a coordinated campaign by a single actor, or a shared third-party or supply chain vector that connected them. Japan's regulatory disclosure requirements have tightened, so we might be seeing faster reporting, but the volume is unusual.

Alex: If you have Japanese subsidiaries, joint ventures, or tier-one suppliers in Japan, this is your signal to assess exposure. Don't wait for attribution. Check your data flows, check your shared service providers, and verify your incident notification agreements with Japanese partners are current.

Jordan: Now let's shift to a story that's going to reshape how we think about AI security tools. The Commerce Department reached an agreement with Anthropic to lift export controls on its Mythos and Fable frontier AI models. These were restricted because of dual-use concerns — specifically, jailbreak vulnerabilities that could enable adversarial applications.

Alex: The lift is conditional. Anthropic says they've implemented new classifiers and guardrails that block the original jailbreak technique in over 99 percent of cases. And Commerce apparently accepted that as sufficient. What's significant here isn't just this specific decision — it's that this creates a precedent. A conditional release framework for frontier AI capabilities. Other AI companies are watching this very closely.

Jordan: From a CISO perspective, there are two angles. First, if you're evaluating AI-powered security tools, the vendor landscape just changed. Models that were previously restricted are now available, which means your procurement evaluation criteria need to account for what guardrails are actually in place and how they're validated. Second, if you're doing adversarial AI threat modeling, the capabilities available to both defenders and attackers just expanded. The 99 percent block rate sounds impressive until you think about what the remaining one percent enables at scale.

Alex: And for CISOs sitting on AI governance committees — which should be all of you at this point — this regulatory model matters. Conditional release with technical guardrails is going to be the template. Your AI risk frameworks need to accommodate it.

Jordan: Let's talk about Microsoft's post-quantum announcement, because this one changes planning timelines. Mark Russinovich, Azure's CTO, announced they're targeting 2029 for full quantum-safe cryptography deployment across Azure. That's an acceleration from their previous roadmap.

Alex: This is a big deal for any enterprise that runs on Azure, which is a significant portion of the Fortune 500. When your primary cloud provider says the risk horizon has shifted and they're moving faster, you need to move faster too. If your PQC transition plan was built around a 2032 or 2035 timeline, you're now potentially out of sync with your infrastructure provider.

Jordan: The subtext here is that Microsoft is treating harvest-now-decrypt-later as a near-term operational risk, not a theoretical academic exercise. They have visibility into threat intelligence that most enterprises don't. When they accelerate, it's worth asking what they're seeing that's driving the urgency.

Alex: The practical implication: CISOs need to inventory every cryptographic dependency in their environment, identify what's quantum-vulnerable, and build a migration roadmap that aligns with — or ideally leads — their cloud provider's timeline. If you haven't started that work, 2029 is going to arrive faster than you think.

Jordan: Three years is not a lot of time for a cryptographic migration across enterprise infrastructure. This is a program that needs executive sponsorship and budget now.

Alex: Last two stories, and they're connected. DHS is launching ANCHOR-CI — the Alliance of National Councils for Homeland Operational Resilience for Critical Infrastructure. This is the replacement for the public-private information sharing council that was shut down over a year ago. And separately, OMB Director Russell Vought has signaled openness to re-staffing CISA with roughly 600 personnel after deep cuts.

Jordan: So the government broke the information sharing mechanism, let CISA atrophy, and is now trying to rebuild both. I'll skip the editorial on the wisdom of that sequence. What matters for CISOs is whether the replacement is actually functional or just a rebrand.

Alex: If you're in a critical infrastructure sector — energy, financial services, healthcare, water, transportation — you need to evaluate whether your organization should engage with ANCHOR-CI. The original council, for all its imperfections, was a real channel for actionable threat intelligence. Its absence has been felt. If this replacement can deliver even partial capability, it's worth participating.

Jordan: On the CISA re-staffing, 600 people is meaningful. CISA's advisory and incident response capacity was genuinely degraded by the cuts. If those positions come back, the agency's value as a resource to enterprise security programs improves. But staffing decisions are slow, and the threat environment isn't waiting.

Alex: Alright, let's talk about what we're watching. Jordan, when you look at this week's landscape, what's the thread?

Jordan: It's convergence under pressure. You've got active exploitation campaigns on Oracle, a zero-day dump accelerating the attacker's advantage, a massive automated campaign against cloud control planes, and a wave of breaches in Japan suggesting supply chain compromise. At the same time, the institutional infrastructure that's supposed to help — DHS, CISA, public-private coordination — is being rebuilt mid-crisis. And the technology landscape is shifting under everyone's feet with quantum timelines compressing and AI capabilities expanding. CISOs are being asked to manage compounding, simultaneous risk with structures that are still under construction.

Alex: I'd add that the Oracle situation specifically is something to watch over the next two weeks. Two product lines under active exploitation, confirmed victims at the scale of Nissan — this campaign isn't done. If you're an Oracle shop, treat this as your top priority this week.

Jordan: And keep an eye on what comes out of that zero-day cache. The exploit brokers and opportunistic actors are going to move fast. Your threat intel feeds should be on fire right now. If they're not, ask why.

Alex: That's our show for today. Show notes, links to every story we covered, and our source list are all at cleartext.fm. We'll be back tomorrow. Stay sharp.

Jordan: See you then.

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

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 10 stories across 5 topic areas, including: US posts $10 million reward over Russian cyber campaign targeting Signal, WhatsApp; Mustang Panda Uses Zoho WorkDrive as Command Channel in Indian Government Attacks; The attack that hijacked Claude Code came through Sentry. Datadog, PagerDuty, and Jira have the same exposure..

The Record (Recorded Future) · Jun 29 · Relevance: █████████░ 9/10

Why it matters to CISOs: Russia-linked APT groups UNC5792 and UNC4221 are actively targeting government officials via secure messaging platforms, representing a significant threat to executive communications security and mobile device policies at any organization with government ties or sensitive communications requirements.

📖 Read full article

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

Why it matters to CISOs: China-aligned Mustang Panda's use of legitimate SaaS platforms like Zoho WorkDrive as C2 infrastructure demonstrates an evolving evasion technique that defeats network-based controls and highlights the risk of trusted cloud services being weaponized against enterprise and government targets.

📖 Read full article

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

Why it matters to CISOs: The 'agentjacking' attack class—where attackers inject malicious instructions into observability and ticketing tools to hijack AI coding agents—exposes enterprises adopting agentic AI development workflows to a systemic new threat that bypasses EDR, WAF, IAM, and firewall controls entirely.

📖 Read full article

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

Why it matters to CISOs: Active exploitation of a CVSS 9.8 authentication and privilege management flaw in Oracle E-Business Suite's Payments module threatens financial data integrity and ERP system availability at enterprises running one of the most widely deployed back-office platforms globally.

📖 Read full article

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

Why it matters to CISOs: Nissan's disclosure of an employee data breach via Oracle PeopleSoft zero-day exploitation by ShinyHunters reinforces the urgent need for CISOs to assess PeopleSoft exposure and patch status, especially as the same attack vector has now hit multiple major organizations.

📖 Read full article

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

Why it matters to CISOs: Aflac's breach via a Japan subsidiary underscores the persistent risk of subsidiary and international entity security gaps creating enterprise-wide exposure, particularly for personal and financial data subject to cross-border regulatory obligations.

📖 Read full article

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

Why it matters to CISOs: The Supreme Court's Chatrie ruling requiring warrants for geofence location data materially changes how enterprises must respond to law enforcement data requests and may affect data retention policies for any systems that collect or process location information at scale.

📖 Read full article

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

Why it matters to CISOs: Senator Warner's draft AI Agent Act would require FTC-vetted certification for AI agent software vendors, creating a potential new compliance layer for enterprises procuring or deploying AI agents and putting AI vendor due diligence directly on security and procurement teams.

📖 Read full article

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

Why it matters to CISOs: CISA confirmation of active ransomware exploitation of a Windows Defender privilege escalation vulnerability means every enterprise Windows environment is at risk; immediate patch validation and threat hunting are warranted given the ransomware delivery vector.

📖 Read full article

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

Why it matters to CISOs: A CVSS 10.0 authentication bypass in SimpleHelp RMM—widely used by MSPs managing enterprise environments—is being actively exploited to deliver a cross-platform stealer targeting cloud, AI, and DevOps credentials, creating supply chain exposure for any enterprise relying on managed service providers.

📖 Read full article

Alex: Welcome to Cleartext for Tuesday, June 30th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Jordan: So here's where we're starting today. Sentry, the error monitoring tool that lives in basically every modern dev shop, was used to hijack AI coding agents. Claude Code, Cursor, Codex. A single crafted error event, sent through a public credential, and the agent executes attacker instructions with full developer privileges. Eighty-five percent success rate in testing. EDR didn't catch it. WAF didn't catch it. IAM didn't catch it. Sentry's own response was, and I'm quoting here, "technically not defensible." That's the phrase that should keep you up tonight.

Alex: That is a hell of a way to start the show. We're going to dig into that one. We've also got active ransomware exploitation of a Windows Defender flaw that CISA just flagged, a ten-million-dollar bounty on Russian hackers targeting Signal and WhatsApp, Oracle E-Business Suite under active attack, Nissan disclosing a breach tied to Oracle PeopleSoft zero-days, Mustang Panda weaponizing Zoho WorkDrive against India, a Supreme Court ruling that's going to change how you handle law enforcement data requests, and a Senate bill that wants to create a federal registry for AI agents. It's a packed day. Let's get into it.

Alex: Jordan, let's start with the agentjacking story because this feels like a category-defining moment for anyone deploying agentic AI in their development pipeline.

Jordan: It is. And the reason I led with it is that this isn't a theoretical attack. Tenet Security demonstrated it. The Cloud Security Alliance has already classified agentjacking as a systemic MCP vulnerability class. The attack surface here is every integration point between an AI coding agent and the tools it consumes data from. Sentry, Datadog, PagerDuty, Jira. These are all tools that feed context into agentic workflows. An attacker poisons that context, and the agent treats it as legitimate instruction. There's no malware signature to detect. There's no anomalous network traffic. The agent is doing exactly what it's designed to do, just with instructions from the wrong person.

Alex: And this is the part that boards need to understand. We've spent decades building security architectures around the assumption that humans read the input and make decisions. AI agents don't have that filter. They ingest and execute. So every data source that feeds an agent is now a trust boundary, and most organizations haven't mapped those boundaries, let alone defended them.

Jordan: Right. And the fix isn't simple. You can't just patch Sentry. The problem is architectural. If your AI agent trusts data from any external system without verification, you have this exposure. Period. The practical step right now is inventory. Know which AI agents are running in your environment, what data sources they consume, and what privileges they hold. If you can't answer those three questions, you have an unmanaged risk.

Alex: And I'd add, if you're in a board conversation about AI productivity gains, this is the counter-narrative you need to present. The productivity comes with a new threat surface that existing controls don't address. Budget accordingly.

Jordan: Let's pivot to the geopolitical block because we've got two stories that rhyme in important ways. First, the State Department posting a ten-million-dollar reward for information on UNC5792 and UNC4221, two Russian groups that have been compromising government officials' Signal and WhatsApp accounts through social engineering.

Alex: The CISO takeaway here isn't just about government targets. If your executives communicate sensitive business information over Signal or WhatsApp, and let's be honest, they all do, you need to treat those platforms as part of your attack surface. The fact that nation-state actors are specifically targeting secure messaging apps tells you something. These apps are where the high-value conversations happen, and adversaries know it.

Jordan: And the attack vector is social engineering, not cryptographic compromise. They're not breaking Signal's encryption. They're tricking people into linking devices or approving access. So your technical controls on the app itself are irrelevant. This is about user awareness and, frankly, about whether your mobile device policy even acknowledges that these apps exist in your environment.

Alex: Most don't. And that's the gap. You've got executives using personal devices running consumer messaging apps for board-level discussions, M&A conversations, regulatory strategy. None of it's in your MDM. None of it's in your DLP. And now you've got Russian intelligence services actively targeting that exact blind spot.

Jordan: The second geopolitical story is Mustang Panda, China-aligned, running espionage campaigns against Indian government networks and using Zoho WorkDrive as their command-and-control channel. This is the living-off-trusted-services play. Malicious traffic blends perfectly with legitimate SaaS communications.

Alex: This is a trend that's been building for two years, and it's now fully mature. When your C2 traffic looks like a file sync to Zoho or OneDrive or Google Drive, your network-based detection is effectively blind. The implication for CISOs is that you need behavioral analytics at the endpoint level, not just network monitoring. And you need to seriously evaluate which SaaS platforms are allowed to communicate with sensitive segments of your environment.

Jordan: They're also deploying new malware families, which tells you Mustang Panda is investing in capability development. This isn't a one-off campaign. It's an ongoing program with resources behind it. If your organization operates in South or Southeast Asia or has supply chain exposure there, this is directly relevant.

Alex: Now let's talk Oracle, because we essentially have two Oracle stories that together paint a pretty alarming picture. First, CVE-2026-46817, a CVSS 9.8 in Oracle E-Business Suite's Payments module, actively exploited in the wild. Authentication bypass, privilege management bypass, full instance takeover potential.

Jordan: If you run Oracle EBS, and thousands of large enterprises do, this is a drop-everything-and-patch situation. The Payments module means financial data integrity is directly at risk. And the CVSS score isn't theoretical. This is being exploited now, in production, against real targets.

Alex: And then we have Nissan disclosing a breach of employee data tied to Oracle PeopleSoft zero-day exploitation, attributed to ShinyHunters. This is the same attack vector that hit NAIC. It looks coordinated, a campaign targeting PeopleSoft instances across multiple large organizations.

Jordan: ShinyHunters is an extortion group. So expect the data to surface on leak sites if ransom demands aren't met. For CISOs running PeopleSoft, the question isn't whether you're a target. It's whether you've already been compromised and don't know it yet. Patch, then threat-hunt. In that order.

Alex: On the breach front, we also have Aflac disclosing that attackers compromised its Japan subsidiary and stole personal and bank account information. This is the perennial subsidiary risk story. Your security posture is only as strong as your weakest international entity.

Jordan: And Japan's APPI has teeth. Cross-border data breach obligations are real. If you're a multinational, your subsidiary governance model is either a security program or it's a liability. There's no middle ground anymore.

Alex: Let's hit the two vulnerability stories. Jordan, BlueHammer first.

Jordan: CISA confirmed Monday that ransomware gangs are actively exploiting a Windows Defender privilege escalation vulnerability they're calling BlueHammer. This was a zero-day before ransomware operators picked it up, and now it's in active ransomware campaigns. Windows Defender is on virtually every enterprise Windows endpoint. This is near-universal exposure. Validate your patches. If you're behind on the June cycle, this one alone justifies emergency remediation.

Alex: And SimpleHelp?

Jordan: CVE-2026-48558. CVSS 10. Authentication bypass in SimpleHelp's remote monitoring and management platform. Actively exploited to drop a cross-platform stealer called Djinn that targets cloud credentials, source control tokens, AI development tool keys, SSH keys, the whole crown jewels inventory. Here's the wrinkle: SimpleHelp is widely used by managed service providers. So even if you don't run it yourself, your MSP might. And that makes this a supply chain problem. Ask your MSPs today whether they use SimpleHelp and whether they've patched.

Alex: Good. Two governance stories to close out the segments. The Supreme Court ruled in Chatrie that police need a warrant to request geofence location data from third parties. This reverses the prior third-party doctrine application for location data.

Jordan: The dissent called it "seismic," and they're not wrong. For CISOs, the practical impact is on how you handle law enforcement data requests. If your systems collect or process location data at scale, and many enterprise apps do, your legal and compliance teams need to update their response playbooks. You may also want to revisit data retention policies for location information. Less data retained means less data to argue about in court.

Alex: And finally, Senator Warner's draft AI Agent Act, which would empower the FTC to create a registry certifying AI agent software vendors on privacy and cybersecurity protections. If you're procuring or deploying AI agents, this bill signals where the regulatory wind is blowing.

Jordan: It's a draft. It hasn't passed. But the direction is clear. Congress wants a compliance layer around AI agent procurement. If your organization is buying AI agent capabilities today, start documenting your vendor due diligence now. When the regulation lands, and some version of it will, you don't want to be scrambling.

Alex: Let's zoom out for the outlook. Jordan, what's the thread you're pulling on this week?

Jordan: Trust boundaries. Every major story today is fundamentally about trust boundaries being violated or redefined. AI agents trusting poisoned data from observability tools. Secure messaging apps being compromised through social engineering. Legitimate SaaS platforms being weaponized as C2 channels. Subsidiaries creating enterprise-wide exposure. MSP tools becoming supply chain attack vectors. The common theme is that the things we implicitly trust, our tools, our vendors, our subsidiaries, our communication platforms, are exactly what adversaries are targeting. The 2026 CISO challenge is making trust explicit and verifiable rather than assumed.

Alex: I'd add the governance dimension. Between the Supreme Court ruling and the Warner bill, we're seeing the legal and regulatory framework trying to catch up with these same trust questions. Who can access what data under what conditions? Who's accountable when an AI agent acts on bad input? These aren't abstract policy debates anymore. They're operational questions that land on the CISO's desk. If you're not already embedded in your organization's legal and policy conversations about AI and data governance, you're behind.

Jordan: And I'll leave listeners with one tactical takeaway: this week, map your AI agent integrations. Every tool that feeds data to an AI agent in your environment is a potential injection point. If you don't have that inventory, building it is your highest-leverage activity this week.

Alex: That's Cleartext for Tuesday, June 30th, 2026. Show notes and links to every story we covered today 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-30.

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 9 stories across 5 topic areas, including: US offers $10 million reward over Russian cyber campaign targeting Signal, WhatsApp; Russian Hackers Accused of Destructive Cyber-Attack on Jaguar Land Rover; Gamaredon Expands Ukraine Attacks with New Malware and Cloud Service Abuse.

The Record (Recorded Future) · Jun 29 · Relevance: █████████░ 9/10

Why it matters to CISOs: Russian GRU/FSB-linked groups socially engineering access to encrypted messaging platforms used by senior officials signals a direct threat to executive communications channels at enterprises with government exposure. CISOs should immediately audit use of Signal and WhatsApp by board members and senior leadership.

📖 Read full article

Infosecurity Magazine · Jun 29 · Relevance: ████████░░ 8/10

Why it matters to CISOs: A destructive ransomware attack attributed to Kremlin-backed actors against a major multinational manufacturer signals escalating Russian cyber operations beyond government targets into critical industrial and corporate sectors. CISOs at large manufacturers and critical infrastructure organizations should elevate threat levels.

📖 Read full article

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

Why it matters to CISOs: Gamaredon's 35 documented spear-phishing campaigns and expanded malware arsenal—including abuse of legitimate cloud services for C2—represent TTPs that routinely spill over from conflict-zone targets into Western enterprise supply chains and partners.

📖 Read full article

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

Why it matters to CISOs: The US government's decision to gate access to OpenAI's most capable cybersecurity-focused AI model signals a new era of AI export controls and dual-use AI governance that will shape enterprise security tooling procurement and vendor risk assessments.

📖 Read full article

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

Why it matters to CISOs: Mozilla's 0DIN proof-of-concept demonstrates that malicious repositories can silently hijack AI coding agents like Claude Code to compromise developer machines without any malicious code—a novel supply chain vector that enterprises deploying AI-assisted development must immediately assess and govern.

📖 Read full article

Infosecurity Magazine · Jun 29 · Relevance: █████████░ 9/10

Why it matters to CISOs: A zero-day exploit against Oracle PeopleSoft compromising the NAIC—the body that sets standards for the US insurance regulatory framework—has direct implications for financial sector CISOs managing regulatory data and PeopleSoft deployments.

📖 Read full article

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

Why it matters to CISOs: Exposure of 14.2 million email credentials across six ISPs creates immediate credential stuffing risk for enterprise organizations whose employees use personal ISP email accounts linked to corporate identities or reuse passwords, and warrants proactive dark web monitoring and MFA enforcement review.

📖 Read full article

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

Why it matters to CISOs: Federal PQC migration deadlines of 2030 and 2031 create a multi-year transformation program that most enterprise security teams have not yet begun, making this an urgent board-level conversation about cryptographic risk and capital planning.

📖 Read full article

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

Why it matters to CISOs: Oracle E-Business Suite is widely deployed in large enterprise financial operations; active exploitation of CVE-2026-46817 in ERP and financial systems demands immediate patching prioritization and threat hunting in affected environments.

📖 Read full article

Alex: ...

Jordan: Monday morning, and the US government is putting a ten million dollar bounty on Russian hackers who figured out you don't need to break encryption if you can just social engineer your way into someone's Signal account. That's where we start today.

Alex: Welcome to Cleartext. It's Monday, June 29th. I'm Alex Chen, alongside Jordan Reeves. We've got a packed show. Russian cyber operations are escalating on multiple fronts, from encrypted messaging platforms to destructive attacks on major manufacturers. We'll cover a federal insurance regulator breached through an Oracle zero-day, Oracle again under active exploitation in E-Business Suite, Mozilla raising red flags about AI coding agents as a novel supply chain vector, the government gating access to OpenAI's new cybersecurity model, and why your post-quantum migration clock is ticking louder than you think. Let's get into it.

Jordan: So let's start with this State Department bounty. Ten million dollars for information on two groups, UNC5792 and UNC4221, both linked to Russian intelligence services. What they're doing is targeting Signal and WhatsApp accounts of government officials, but here's what matters for our audience: they're not breaking the encryption. They're exploiting account linking features and backup mechanisms through social engineering. They're going after the human layer and the platform design choices that sit around the cryptography.

Alex: And this is directly relevant if you're a CISO at any organization where senior leadership or board members use encrypted messaging for sensitive business communications. Which is basically every large enterprise at this point. The assumption that Signal or WhatsApp equals secure is dangerously incomplete. The encryption is sound. The account management, the backup configurations, the device linking workflows, those are the attack surface. If you haven't audited how your executives are using these platforms, how their accounts are configured, whether they've linked devices they've forgotten about, this is your prompt to do it this week.

Jordan: The ten million dollar bounty tells you where the US government ranks this threat. That's not a routine number. That's reserved for operations they consider strategically significant. And it tracks with what we're seeing more broadly from Russian cyber operations right now, which is a clear escalation across multiple vectors simultaneously.

Alex: Which brings us directly to the Jaguar Land Rover attack. A destructive cyberattack attributed to Kremlin-backed actors. Not ransomware for profit. Destructive. Novel ransomware variants with deliberate attribution obfuscation.

Jordan: This is important to parse carefully. When we say destructive with attribution obfuscation, what that means operationally is the attackers wanted to cause damage and make it hard to prove who did it. That's a different playbook than criminal ransomware. Criminal groups want you to know who they are so you pay them. State actors deploying destructive capability behind false flags are sending a geopolitical message while maintaining deniability. The strategic timing here aligns with broader Russian patterns of hitting Western corporate targets during periods of diplomatic tension.

Alex: For CISOs at large manufacturers, critical infrastructure, anyone in the automotive supply chain, this is a direct signal to elevate your threat posture. The conversation with your board should be explicit: state-sponsored destructive attacks against Western corporations are not theoretical. They're happening to household names. Your incident response plans need to account for scenarios where the attacker's objective is destruction, not monetization.

Jordan: And rounding out the Russia picture, Gamaredon, which ESET has documented running thirty-five distinct spear-phishing campaigns against new targets throughout 2025. They've expanded their malware arsenal and, critically, they're abusing legitimate cloud services for command and control.

Alex: The cloud C2 piece is what I want CISOs to focus on. When your threat actors are tunneling command and control through services that your firewalls and proxies are configured to trust, your standard network detection controls have a significant blind spot. This is a TTP that routinely spills over from conflict-zone targeting into Western enterprise supply chains, particularly if you have any partners, subsidiaries, or operations touching Eastern Europe.

Jordan: Three Russian stories, three different attack vectors, one coherent escalation pattern. That's the macro picture this Monday morning.

Alex: Let's shift to the NAIC breach, because this one has direct financial sector implications. The National Association of Insurance Commissioners, which sets regulatory standards for the entire US federal insurance system, confirmed that attackers exploited a zero-day in Oracle PeopleSoft to access their IT systems.

Jordan: The nature of the target matters as much as the exploit here. NAIC holds sensitive regulatory data, industry standards, examination information. If you're a CISO at an insurance company or any financial institution that interacts with NAIC regulatory frameworks, you need to be asking what data was exposed and whether it has downstream implications for your organization's regulatory posture.

Alex: And this connects directly to our next story. CVE-2026-46817, a critical vulnerability in Oracle E-Business Suite, now under active exploitation. Threat intelligence from Defused confirms attackers have moved from proof of concept to active campaigns. Oracle EBS runs financial operations, HR, supply chain for thousands of large enterprises.

Jordan: Two Oracle enterprise products, PeopleSoft and E-Business Suite, both under active targeted attack simultaneously. If you're running either of these, patch prioritization is not a debate. It's an emergency. And if your patching cycle for Oracle is quarterly, you need to have a conversation about whether that cadence is survivable in this threat environment.

Alex: The action items are straightforward. Immediate patching for CVE-2026-46817 if you're on E-Business Suite. Threat hunting in your PeopleSoft environments. And an honest assessment of your Oracle patching velocity relative to the speed at which these vulnerabilities are being weaponized.

Jordan: Let's talk about something that's going to reshape how CISOs think about their development pipelines. Mozilla's Zero Day Investigative Network published a proof of concept showing that a malicious GitHub repository can compromise a developer's machine through AI coding agents, specifically Claude Code, without containing a single line of malicious code.

Alex: I want to make sure that lands properly. No malicious code in the repository. The attack uses indirect prompt injection to manipulate the AI agent into taking harmful actions on the developer's machine. Your static analysis tools won't catch it. Your code review process won't catch it. Because there's nothing malicious to find in the code itself.

Jordan: The attack surface here scales with adoption. Every enterprise that's rolling out AI-assisted development, and that's most of you at this point, has just inherited a novel supply chain risk that your existing controls were not designed to address. The AI agent becomes the vulnerability. It reads context from the repository, gets manipulated by crafted content, and then acts with whatever permissions it's been granted on the developer's workstation.

Alex: If you're a CISO who's been approving AI coding tool rollouts, and you should be, because the productivity gains are real, you now need a governance framework around what those agents can do, what permissions they operate with, and how you're monitoring their behavior. This isn't about blocking adoption. It's about establishing guardrails before this vector gets weaponized at scale.

Jordan: And speaking of AI governance, OpenAI is previewing GPT-5.6 Sol, which they're positioning as their flagship cybersecurity-oriented model, exclusively to vetted partners at the US government's request before broader release.

Alex: This is a watershed moment. The US government is treating advanced AI cybersecurity capabilities as strategically sensitive dual-use technology. Gated access. Export control dynamics. This will directly affect your procurement. If you're evaluating AI-powered security tools, the most capable models may come with access restrictions, compliance requirements, and geopolitical considerations that didn't exist six months ago.

Jordan: It also creates a two-tier market. Organizations with government relationships and appropriate clearances get early access to the most capable defensive tools. Everyone else waits. CISOs need to factor that asymmetry into their AI security strategy and vendor evaluation processes.

Alex: Let's close our coverage with post-quantum cryptography, because the CyberScoop piece on the executive order deadlines deserves attention. Federal PQC migration deadlines are set for 2030 and 2031. That sounds far away. It is not.

Jordan: Four years to inventory every cryptographic asset in your environment, evaluate quantum-vulnerable implementations, plan migration paths, test compatibility, and execute the transition. Most organizations haven't started step one. And the harvest-now-decrypt-later threat means adversaries are already collecting your encrypted data today, betting they'll be able to decrypt it with quantum capabilities within a decade.

Alex: This is a board-level capital planning conversation. PQC migration is not a technology project. It's a multi-year transformation program that touches every system, every protocol, every certificate, every key. If you haven't started the cryptographic inventory, you're already behind the curve. The window for orderly execution is closing, and disorderly execution of cryptographic transitions is how you break production systems.

Jordan: Briefly on the KDDI breach in Japan. Fourteen point two million email credentials exposed across six ISPs sharing common infrastructure. The shared infrastructure model amplified the blast radius dramatically.

Alex: The enterprise angle is credential stuffing. Your employees have personal email accounts at ISPs. If they've reused passwords or linked those accounts to corporate identities, this breach feeds directly into attacks against your SSO portals, your VPN gateways, your cloud tenants. Proactive dark web monitoring and an MFA enforcement audit are warranted.

Jordan: Looking at the week ahead, Alex, there's a clear theme. The perimeter of what CISOs have to defend keeps expanding in ways that traditional security architecture wasn't built for. AI coding agents as attack vectors. Encrypted messaging platforms compromised through social engineering. Cloud services weaponized for C2. State actors deploying destructive capability against commercial targets.

Alex: The common thread is that the trust assumptions embedded in our architectures are being systematically exploited. We trust encrypted messaging. We trust AI agents to read code safely. We trust cloud services. We trust that our Oracle patches can wait until the quarterly cycle. Every one of those assumptions took a hit today. The CISOs who will navigate this well are the ones having honest conversations with their boards about which trust assumptions they're still carrying and which ones need to be revisited.

Jordan: And doing it with urgency. Because the adversaries on the other side of these stories aren't waiting for your next board meeting.

Alex: That's our show for Monday, June 29th. 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-29.

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

Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 17 stories across 5 topic areas, including: Amadey and StealC Malware Network Disrupted, 27M Stolen Credentials Recovered; FBI Warns Russian Intelligence Hackers Target Signal Backup Recovery Keys; Russia uses Cellebrite to break into human rights activist’s phone, even after cancellation of contract.

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

Why it matters to CISOs: Operation Endgame's simultaneous takedown of two malware-as-a-service platforms — dismantling 200+ C2 servers and recovering 27 million credentials — sets a new precedent for coordinated public-private disruption operations and signals continued pressure on the ransomware supply chain.

📖 Read full article

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

Why it matters to CISOs: Russian intelligence has evolved its Signal phishing campaign to harvest Backup Recovery Keys, giving persistent, account-level access to historical encrypted messages — a critical threat for any executive or security team member using Signal for sensitive communications.

📖 Read full article

CyberScoop · Jun 25 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: Citizen Lab's confirmation that Russian authorities used Cellebrite tools post-contract-termination exposes a critical gap in vendor end-of-life controls for dual-use surveillance technology — CISOs should reassess assumptions that commercial vendor off-boarding stops state adversary tool use.

📖 Read full article

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

Why it matters to CISOs: A 50%+ rise in ransomware attacks targeting European organizations, with third-party suppliers as the primary entry point, is directly relevant to any CISO operating in or with supply chains connected to EU markets — especially given NIS2 enforcement and DORA compliance obligations.

📖 Read full article

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

Why it matters to CISOs: A researcher-built fake skill that bypassed all tested AI agent security scanners and reached 26,000 agents — including corporate accounts — demonstrates that AI agent marketplaces are a nascent but materially uncontrolled attack surface that most enterprise security programs have not yet addressed.

📖 Read full article

Infosecurity Magazine · Jun 25 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: A 20-percentage-point collapse in organizational reliance on AI-only vulnerability scanning is a direct signal to CISOs evaluating AI security tooling ROI — the market is course-correcting toward human-AI hybrid models, with implications for vendor selection and board-level AI security narratives.

📖 Read full article

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

Why it matters to CISOs: The guilty pleas from two core Scattered Spider members — responsible for the 2024 Transport for London attack — mark a landmark legal accountability moment for a group that has targeted enterprise social engineering at scale; CISOs should note the conviction validates that SIM-swap and vishing TTPs now carry serious criminal consequences.

📖 Read full article

Cybersecurity Dive · Jun 23 · Relevance: █████████░ 9/10

Why it matters to CISOs: The Klue breach is a textbook third-party OAuth token risk: a four-year-old credential from a forgotten pilot was used to pivot into Salesforce environments at Huntress, HackerOne, Jamf, Recorded Future, Tanium, and LastPass — directly hitting the security vendor ecosystem CISOs rely on.

📖 Read full article

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

Why it matters to CISOs: FortiBleed's scope is expanding — attackers have weaponized 430,000 compromised FortiGate firewalls as active credential sniffers, making this an ongoing network intelligence operation, not just a patch-and-move-on event; any enterprise running FortiGate should assume traffic visibility is compromised until forensically cleared.

📖 Read full article

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

Why it matters to CISOs: The Polymarket incident — a malicious script injected via a breached third-party vendor reaching the platform's frontend — is a vivid reminder that software supply chain integrity controls must extend to every vendor with write access to production assets, not just direct code contributors.

📖 Read full article

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

Why it matters to CISOs: A confirmed breach at Tata Electronics — a primary manufacturer in Apple and Tesla supply chains — raises fourth-party risk concerns for any enterprise whose technology procurement flows through these vendors, and reinforces that supply chain cyber risk extends well beyond software into physical hardware manufacturing.

📖 Read full article

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

Why it matters to CISOs: The executive order creates hard regulatory deadlines (key establishment by 2030, digital signatures by 2031) that will cascade into federal contractor requirements and vendor certification demands, forcing CISOs at companies with government exposure to accelerate PQC roadmaps now.

📖 Read full article

CyberScoop · Jun 25 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: FCC's new mandatory cybersecurity requirements for emergency alert distributors and undersea cable operators represent a shift from voluntary guidance to enforceable standards for critical communications infrastructure — relevant for CISOs at telecom, ISP, and media organizations.

📖 Read full article

The Record (Recorded Future) · Jun 25 · Relevance: ██████░░░░ 6/10

Why it matters to CISOs: After months of CISA operating without a Senate-confirmed director, confirmation that a nominee is imminent — alongside plans to hire 600 staff — signals a potential reset in federal cyber leadership that will affect agency relationships, information sharing, and regulatory posture for enterprise CISOs.

📖 Read full article

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

Why it matters to CISOs: CVE-2026-20230 in Cisco Unified Communications Manager is unauthenticated and remotely exploitable (CVSS 8.6), now actively attacked with a public PoC — CISA's Sunday patch deadline for federal agencies makes this an emergency patching event for any enterprise running UCM infrastructure.

📖 Read full article

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

Why it matters to CISOs: Mandiant's finding that this Cisco SD-WAN zero-day was exploited two months before public disclosure — at a communications service provider — suggests a sophisticated threat actor with pre-patch intelligence, underscoring that KEV patching timelines alone are insufficient when adversaries have zero-day access.

📖 Read full article

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

Why it matters to CISOs: The Cordyceps CI/CD workflow pattern affects repositories at Microsoft, Google, Apache, and hundreds of other major organizations — CISOs overseeing software development must audit pull_request_target usage in GitHub Actions workflows immediately, as this is an exploitable class vulnerability not a one-off.

📖 Read full article

Jordan: If I had to pick one word for this week, it's supply chain. Not as a buzzword — as an actual, live, multi-front crisis. A four-year-old OAuth token from a forgotten pilot program let attackers pivot through Salesforce integrations at Huntress, HackerOne, Jamf, Recorded Future, Tanium, and LastPass. Half the security vendor ecosystem got hit because nobody revoked a credential from 2022. Meanwhile, four hundred and thirty thousand FortiGate firewalls are actively sniffing credentials, Cisco has two critical vulns under active exploitation, and a fake AI agent skill waltzed past every marketplace scanner to reach twenty-six thousand agents. If your security model depends on trusting your vendors, your tools, and your infrastructure — and whose doesn't — this was the week that trust got stress-tested hard.

Alex: Welcome to the Cleartext 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're going to cover four themes today. First, the supply chain reckoning — from the Klue breach to FortiBleed to Tata Electronics, third-party risk went from theoretical to visceral this week. Second, the geopolitical landscape — a major botnet takedown, Russian intelligence evolving its Signal targeting, and uncomfortable questions about surveillance tool controls. Third, governance and deadlines — a post-quantum executive order with hard dates, new FCC rules, and movement on CISA leadership. And fourth, the emerging AI attack surface and what the market is telling us about trust in AI security tooling. Let's get into it.

Jordan: So let's start with supply chain, because this week was a masterclass in how third-party risk actually materializes. The Klue breach is the one I want CISOs to sit with. An attacker used a credential from a 2022 pilot integration — a pilot that apparently ended, but the OAuth token was never revoked. Four years later, that token opened the door to Salesforce environments at companies whose entire business is security. Huntress. HackerOne. Recorded Future. LastPass, which really cannot catch a break. And then a second threat group piled on with a ransom demand.

Alex: What makes this one sting is the victim list. These aren't companies that lack security maturity. These are security companies. And the lesson isn't that they're incompetent — it's that the problem is structural. Every enterprise has hundreds of SaaS integrations, many from pilots and POCs that went nowhere. The OAuth tokens persist. The Salesforce connections persist. Nobody owns the lifecycle. If your identity governance program doesn't cover third-party OAuth grants with the same rigor as employee accounts, you have this exact exposure right now.

Jordan: And then layer FortiBleed on top. This isn't a new vulnerability — it's the ongoing exploitation campaign where attackers deployed a Golang-based credential sniffer across roughly four hundred and thirty thousand compromised FortiGate firewalls. A hundred and ten million credentials harvested. These aren't firewalls that got popped and patched. They're firewalls that are actively operating as intelligence collection platforms for attackers. If you're running FortiGate and you patched but didn't do forensic validation, you should assume your traffic has been visible to someone else.

Alex: I want to connect that to the Tata Electronics breach. Tata is a primary manufacturer for Apple and Tesla. The details are thin — we don't know the full scope of what was exfiltrated — but the signal matters. Supply chain cyber risk isn't just about software and SaaS anymore. It extends into physical hardware manufacturing. If your iPhones or your fleet vehicles run through a compromised manufacturing partner, that's a fourth-party risk that almost no enterprise risk framework adequately captures.

Jordan: And the Polymarket incident rounds this out nicely. Three million dollars stolen from customers because attackers breached a third-party vendor that had write access to Polymarket's production frontend and injected a malicious script. The vendor wasn't a code contributor. They were just some vendor with access. This is the same pattern over and over — the blast radius of your security is defined by whoever has write access to your production environment, and most organizations don't have a complete inventory of who that is.

Alex: So the through-line for CISOs: this week, conduct an OAuth and API token audit across your SaaS estate. Prioritize tokens from integrations older than twelve months. Revisit your vendor access governance to include every party with write access to production, not just your direct engineering team. And if you're running FortiGate, treat this as an active compromise investigation, not a patching exercise.

Jordan: Let's shift to the geopolitical picture. Operation Endgame was the big coordinated action this week — Europol, Microsoft, Bitdefender, ESET, and Bitsight jointly took down the Amadey and StealC malware-as-a-service infrastructure. Two hundred-plus command-and-control servers. Twenty-seven million stolen credentials recovered. This is the second phase of Endgame; the first hit botnets like Smokeloader last year. What's significant is the targeting — they went after the assembly line, not just the finished product. These are the platforms ransomware operators use upstream.

Alex: And the timing matters. Black Kite's data showed ransomware attacks against European organizations jumped more than fifty percent in the past year, with third-party suppliers as the primary entry vector. So you've got law enforcement hitting the supply side of ransomware at exactly the moment the demand side is surging in Europe. For CISOs with European operations or EU supply chains, this is a dual pressure — regulatory enforcement under NIS2 and DORA is tightening, while the threat environment is intensifying. The takedowns help, but they're disruptions, not eliminations.

Jordan: On the intelligence side, the FBI and CISA updated their advisory on Russian Signal phishing. The original campaign used linked device tricks — essentially getting a target to scan a QR code that linked the attacker's device to the target's Signal account. Now they've added recovery key theft. If an attacker gets your Signal Backup Recovery Key, they can restore your full message history, read everything, and effectively own the account permanently. The key doesn't expire. It doesn't rotate. One phishing success gives them persistent access.

Alex: This is directly relevant to executive communications. A lot of CISOs and their leadership teams moved to Signal precisely because it's encrypted. But encryption doesn't help if the attacker has your recovery key. If your executives use Signal for sensitive discussions — and many do — you need to issue guidance this week: do not share recovery keys under any circumstances, enable registration lock, and frankly, consider whether Signal's backup model is appropriate for your threat environment.

Jordan: And then there's the Cellebrite story, which is more of a slow burn but important. Citizen Lab confirmed that Russian authorities used Cellebrite phone-cracking tools to access a political opponent's iPhone — after Cellebrite claimed to have terminated its contract with Russia. The tool kept working. The implication for CISOs is broader than Russia: when you off-board a surveillance or forensics vendor, can you actually verify they no longer have capability? The answer, apparently, is often no. Dual-use technology export controls have limited real-world enforcement.

Alex: Let's move to governance, because this week had some consequential regulatory developments. The big one: Executive Order 14409 sets hard deadlines for federal post-quantum cryptography migration. Key establishment algorithms must be in place by December 31, 2030. Digital signatures by December 31, 2031. National security systems are on a separate classified timeline.

Jordan: And for anyone thinking this only matters to federal agencies — it doesn't. These deadlines will cascade into FedRAMP requirements, federal contractor certifications, and vendor qualification criteria. If you sell to the government or you're in the government supply chain, your PQC roadmap just got a hard deadline. 2030 sounds far away until you realize cryptographic migrations in large enterprises take three to five years. The planning window is now.

Alex: The FCC also finalized mandatory cybersecurity rules for emergency alert system distributors and undersea cable operators. This is a shift from voluntary guidance to enforceable requirements — and it's worth noting that these emergency alert systems were successfully hacked back in 2013. It took over a decade to move from incident to enforceable regulation. CISOs in telecom, ISP, and media sectors should review the final rule text.

Jordan: And a quick note on CISA — DHS Secretary Mullin confirmed the president has met with a likely director nominee, with plans to hire six hundred staff once confirmed. After months of the agency operating without Senate-confirmed leadership, this matters for the information sharing relationships and regulatory posture that CISOs depend on. Watch this space.

Alex: On the vulnerability front, two Cisco stories deserve attention together. CVE-2026-20230 in Unified Communications Manager — unauthenticated, remote, CVSS 8.6, actively exploited after a public proof of concept — CISA set a Sunday patch deadline for federal agencies. And CVE-2026-20245 in Catalyst SD-WAN Manager, which Mandiant confirmed was exploited as a zero-day at a communications service provider at least two months before public disclosure. That's root-level access on network infrastructure, pre-patch.

Jordan: The SD-WAN zero-day is the more concerning of the two. Two months of pre-disclosure exploitation at a comms provider suggests a sophisticated actor with access to vulnerability intelligence before the public — whether through independent discovery or something else. This is a reminder that patching on disclosure is necessary but not sufficient. If your threat model includes nation-state actors, you need detection capabilities that don't depend on knowing the specific CVE.

Alex: And quickly on the Cordyceps CI/CD vulnerability — Novee Security found an exploitable pattern in GitHub Actions workflows affecting three hundred-plus repositories at Microsoft, Google, Apache, and others. GitHub pushed a fix on June 18th, but if your engineering teams use pull_request_target triggers, audit those workflows now. This is a class vulnerability, not a single bug.

Jordan: Last theme — AI attack surface. The AIR research firm built a fake AI agent skill, pushed it through a marketplace and an Instagram ad, and it reached twenty-six thousand agents including corporate accounts. Every marketplace security scanner marked it safe. The payload was deliberately benign, but the research proves the full attack chain works at scale. AI agent marketplaces are an uncontrolled attack surface, and most security programs haven't even started thinking about them.

Alex: And on the flip side, Cobalt's study found that only nine percent of organizations now rely solely on AI for vulnerability scanning — down twenty percentage points. The market is course-correcting away from fully autonomous AI security tooling toward human-AI hybrid models. If you're evaluating AI security products or presenting AI security strategy to your board, the narrative has shifted. Pure automation is losing credibility. Human oversight is back in favor.

Jordan: So stepping back — what defined this week? I'd say it was a week where the complexity of modern enterprise dependencies became painfully visible. Supply chain risk isn't one thing — it's forgotten OAuth tokens, compromised firewalls acting as sensors, third-party vendors with production write access, hardware manufacturers in geopolitical crosshairs. It's all of it, simultaneously.

Alex: Agreed. And what I'd add is that this week showed a widening gap between the speed of threat evolution and the speed of institutional response. Russian intelligence is iterating on Signal phishing faster than most security teams update their awareness training. Attackers exploited a Cisco zero-day two months before anyone knew about it. A fake AI skill bypassed every scanner. The defense community is getting better at takedowns and regulation, but the cycle time mismatch is the fundamental challenge. Going into next week, I'd prioritize three things: OAuth and API token hygiene across your SaaS estate, forensic validation of any FortiGate infrastructure, and executive guidance on Signal backup key security. Those are the actions that map to this week's actual threat surface.

Jordan: And if you're in a regulated industry with government exposure, start socializing those post-quantum deadlines internally. 2030 comes fast.

Alex: That's your week in review. The daily show returns Monday. Show notes and links to all stories covered today are at cleartext.fm. I'm Alex Chen.

Jordan: I'm Jordan Reeves. Have a good weekend.

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

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