Daily cybersecurity briefing for CISOs and security leaders.

🎧 Listen to this episode

Today's episode covers 8 stories across 5 topic areas, including: Xi and Putin pledge closer cooperation on AI, cyberspace and satellite systems; Europe dismantles VPN service used by cybercriminals to hide ransomware attacks; Srsly Risky Biz: Politicians ditch Signal for homegrown apps.

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

Why it matters to CISOs: A formal Russia-China pact on AI, cyberspace, and technology independence signals an accelerating bifurcation of the global tech ecosystem — CISOs must factor geopolitical bloc alignment into supply chain risk, vendor selection, and threat modeling.

📖 Read full article

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

Why it matters to CISOs: The takedown of First VPN — a criminal infrastructure service marketed on Russian-speaking forums — demonstrates growing law enforcement capability against anonymization tools used by ransomware operators and may temporarily disrupt attacker operational security.

📖 Read full article

Risky Business News · May 21 · Relevance: ███████░░░ 7/10

Why it matters to CISOs: European governments moving away from Signal to sovereign messaging apps reflects a broader trend of digital sovereignty — CISOs at multinationals must anticipate fragmented secure communications requirements across jurisdictions and assess interoperability risks.

📖 Read full article

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

Why it matters to CISOs: The disruption of Fox Tempest's malware-signing-as-a-service operation — which abused Microsoft's own Artifact Signing system — underscores the risk that trusted code-signing infrastructure can be weaponized, and the importance of verifying software provenance beyond signature checks.

📖 Read full article

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

Why it matters to CISOs: A supply chain attack via a poisoned VS Code extension compromised GitHub's internal repos — this is a wake-up call for every enterprise relying on developer tooling ecosystems and highlights the need to audit IDE extensions, CI/CD pipelines, and enforce least-privilege on developer credentials.

📖 Read full article

Wired Security · May 21 · Relevance: █████████░ 9/10

Why it matters to CISOs: TeamPCP's software supply chain attack spree — impacting hundreds of organizations — demands immediate review of open-source dependency management, software composition analysis tooling, and SBOM practices across the enterprise.

📖 Read full article

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

Why it matters to CISOs: Check Point's acquisition of Deepchecks to validate autonomous AI security agents signals that AI hallucination and reliability in security operations is becoming a board-level concern — CISOs deploying agentic AI in SOCs need validation frameworks.

📖 Read full article

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

Why it matters to CISOs: Active exploitation of SonicWall Gen6 SSL-VPN appliances — with MFA bypass leading to ransomware deployment — is an immediate action item for any enterprise running these widely deployed devices.

📖 Read full article

Jordan: A developer downloaded a VS Code extension. GitHub lost 3,800 internal repositories. And now Lapsus$ is back, selling the data for ninety-five thousand dollars. That's your Thursday.

Alex: Welcome to Cleartext. I'm Alex Chen. With me as always is Jordan Reeves. It's May 21st, 2026, and if you're a CISO right now, your developer toolchain just became your most urgent attack surface. We've got the GitHub breach, a supply chain gang operating at unprecedented scale, a Microsoft malware-signing takedown, SonicWall MFA bypasses tied to ransomware, the Xi-Putin tech alignment pact and what it means for your vendor strategy, European governments abandoning Signal, and a law enforcement win in the criminal VPN space. Let's move.

Jordan: Let's start with the story that's going to dominate your weekend. GitHub got hit. Roughly 3,800 internal repositories were exfiltrated after a single developer installed a poisoned VS Code extension — specifically a compromised version of Nx Console. The root cause traces back to a TanStack npm package that had been tampered with as part of a broader supply chain worm. TeamPCP, now tracked as UNC6780 by threat intelligence teams, is apparently cooperating with Lapsus$ to sell the stolen data for ninety-five thousand dollars.

Alex: And let's be precise about why this one stings. This isn't a zero-day. This isn't a nation-state zero-click exploit. A developer installed an extension from what appeared to be a legitimate source in the VS Code marketplace, and that was enough to compromise one of the most security-conscious engineering organizations on the planet. If you're a CISO and you don't have a policy governing IDE extensions, you have a gap.

Jordan: TeamPCP has been running what researchers are calling the Mini Shai-Hulud supply chain worm — at least seven waves of it since March. The scale is genuinely unusual. Hundreds of organizations hit. And the sophistication is real: they're forging valid cryptographic provenance on malicious packages. So your software composition analysis tools may be telling you everything is signed and clean, and being technically correct while being completely wrong.

Alex: That's the part that should concern boards. We've spent years telling leadership that signed software equals trusted software. TeamPCP just invalidated that assumption at scale. If you have an SBOM program — and you should — audit it now. Not for presence of packages but for integrity of the signing chain. And if you're running open-source dependencies without a formal review process for transitive dependencies, this week is the week to start that conversation with your engineering leadership.

Jordan: Grafana Labs was also caught in this. So it's not GitHub-specific. It's a broad ecosystem compromise, and the blast radius is still being assessed.

Alex: Connected to that ecosystem story — Microsoft this week disclosed it took down a threat actor called Fox Tempest, which had been running a malware-signing-as-a-service operation. And here's the part that matters: they weaponized Microsoft's own Artifact Signing system to get valid Microsoft signatures on malicious code. So we have two separate threat actors, in the same week, demonstrating that code-signing infrastructure is now an active target.

Jordan: This is the logical endpoint of the trust chain being exploited. Defenders built controls that say: verified signature equals permitted execution. Attackers spent years figuring out how to get verified signatures. They've now figured it out. The policy implication is that signature verification is necessary but not sufficient. You need behavioral controls downstream. You need runtime monitoring. A signature check at the perimeter is not the end of the story anymore.

Alex: Patch note for anyone running SonicWall Gen6 SSL-VPN appliances — and there are a lot of them. Active exploitation is occurring right now. Attackers are brute-forcing VPN credentials and then bypassing MFA because SonicWall's patches were incomplete. The outcome is ransomware deployment. This is not a theoretical risk. If you haven't confirmed your SonicWall estate is fully patched — not partially patched — do that today.

Jordan: The incomplete patching detail is what makes this operationally frustrating. Organizations applied the patch, checked the box, and are still exposed. Verify the patch, verify MFA is actually enforced at the appliance level, not just assumed.

Alex: Now let's shift to the geopolitical picture, because the Xi-Putin statement from yesterday deserves more than a headline skim. The joint statement includes explicit pledges to cooperate on satellite internet, software development, and open-source initiatives — framed explicitly as reducing dependence on Western technology and building capacity to compete with countries they describe as unfriendly.

Jordan: From a threat modeling standpoint, this formalizes something that's been directionally true for a while. You now have two major cyber powers explicitly aligning their technology stacks, their AI development, and their cyberspace governance posture. The practical implication is that the technology bifurcation that's been happening quietly for years — Huawei bans, SMIC restrictions, export controls — is now a declared strategic objective on their side too.

Alex: For CISOs at multinationals, this lands in a few different places. Vendor selection and supply chain risk: you need to know where every tier of your technology stack sits relative to these blocs. Board reporting: if you're not already framing geopolitical tech alignment as a risk factor in your briefings, you're behind. And threat modeling: the cooperation between Russian and Chinese capabilities — offensive and defensive — means you may need to revisit your threat actor assumptions, particularly if you're in critical infrastructure, defense industrial base, or any sector subject to export controls.

Jordan: The open-source cooperation piece is also worth watching. If you have engineers pulling from repositories that may increasingly reflect Chinese or Russian development communities, that's a provenance question that connects directly back to the TeamPCP story we just discussed.

Alex: Speaking of fragmentation — European governments are moving away from Signal and building sovereign encrypted messaging platforms. The motivations are legitimate: phishing risk, data sovereignty, vendor dependency on a US-based nonprofit. But the analysts are right to flag the tradeoff. Signal is extraordinarily well-engineered. Homegrown alternatives will introduce their own attack surfaces.

Jordan: For CISOs at multinationals, the practical problem is interoperability. You may soon be operating across jurisdictions where your secure communications stack has to accommodate government-mandated sovereign apps with their own authentication and key management architectures. That's a policy and procurement problem that's worth getting ahead of now.

Alex: Law enforcement had a good week. French and Dutch authorities, with Europol and Eurojust support, seized 33 servers and took down First VPN, a service that had been marketed on Russian-speaking cybercrime forums specifically for ransomware operators and data thieves to evade detection. This is Operation Saffron, and it's significant less for the immediate disruption and more for what it signals about operational tempo.

Jordan: Law enforcement is getting faster and more coordinated on criminal infrastructure. That's not nothing. It temporarily degrades attacker operational security — they have to find new anonymization infrastructure, new tools. It doesn't stop them, but it raises their costs and sometimes surfaces tradecraft that intelligence teams can use.

Alex: Quick note on the vendor side: Check Point acquired Deepchecks, an AI evaluation startup focused on validating autonomous AI agents and preventing hallucinations in security workflows. If you're deploying agentic AI in your SOC — and increasingly you are or you're being sold on doing so — the question of whether those agents are making reliable decisions is not theoretical. This acquisition is Check Point's answer to that question. Watch this space. Validation frameworks for AI-driven security actions will be a requirement within eighteen months.

Jordan: Worth noting that "the AI said so" is not a sufficient answer if an autonomous agent triggers an incident response action that turns out to be wrong. Legal liability, regulatory scrutiny — this matters.

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

Jordan: Trust infrastructure is the attack surface. Code signing, MFA, legitimate developer tools, open-source provenance — the things we built to establish trust in our systems are now the things being targeted. Attackers are not breaking through walls. They're walking through doors we built for ourselves.

Alex: And the geopolitical layer is accelerating this. When you have two major powers formally committing to building a parallel technology ecosystem — including open-source, AI, and satellite infrastructure — the provenance questions that matter for security get harder, not easier. The supply chain problem is going to deepen before it gets better. What I'd tell every CISO going into next week: get a current inventory of your developer toolchain, IDE extensions included. Validate — don't assume — your SonicWall patch state. And if you haven't briefed your board on the Russia-China tech alignment in the context of your specific threat model, schedule that conversation.

Jordan: And maybe double-check what extensions are running in your own VS Code instance before you close the laptop tonight.

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

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

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