Alex: Welcome to Cleartext. It's Thursday, October 8th, 2026. I'm Alex Chen alongside Jordan Reeves, and we have a packed show today. We're going to spend time on a story that should fundamentally change how you think about certificate trust. We'll cover two separate confirmations that AI is now being weaponized offensively — one in influence operations, one in actual financial sector breaches. We've got a critical Atlassian exploitation that needs your attention this morning, regulatory moves on CUI and post-quantum, and a fraud case involving a ransomware recovery firm that's a cautionary tale for every CISO who's ever hired an IR vendor. Jordan, let's get into it.

Jordan: Let's start with the DNS story because this one is architecturally significant. Attackers breached the country-code top-level domain registries for Ghana, Sierra Leone, and American Samoa. Not individual registrars — the registries themselves. The authoritative infrastructure. They then modified DNS records and obtained unauthorized HTTPS certificates for Google domains. Google confirmed their own systems were not breached, but that's almost beside the point.

Alex: Right. The attack didn't need to touch Google. That's what makes this so important. When you compromise a ccTLD registry, you control the authoritative DNS for every domain under that TLD. You can point traffic wherever you want, and critically, you can obtain legitimate certificates from certificate authorities because the CA validation process trusts DNS. So now you have a valid cert for a Google domain, and you can man-in-the-middle encrypted traffic. The entire TLS trust model depends on the integrity of DNS, and this attack just demonstrated that assumption can be broken.

Jordan: And these weren't exactly obscure TLDs. American Samoa, the .as domain, is popular with URL shorteners and tech companies. Any organization with domains under affected ccTLDs was at risk, not just Google. The certificates obtained were technically valid — they'd pass browser checks, they'd pass API TLS validation. Your security stack wouldn't flag them.

Alex: So what should CISOs do? First, if you have any domains under these ccTLDs, assume compromise and audit. Second, this is a good moment to evaluate Certificate Transparency log monitoring. You should be watching for any certificate issuance for your domains. Third, consider CAA records — Certificate Authority Authorization — to restrict which CAs can issue certs for your domains. It's not bulletproof, but it raises the bar. And fourth, think about this as a supply chain risk. Your DNS infrastructure is a dependency, and the security of that dependency is only as strong as the weakest registry in the chain.

Jordan: This is also a geopolitical story. These ccTLD operators are often underfunded national entities or small contracted operators. They're soft targets. And if a nation-state wanted to intercept traffic at scale — diplomatic communications, financial transactions routed through affected domains — this is the playbook. We should expect this technique to be repeated against other ccTLDs.

Alex: Let's pivot to AI being used offensively, because we have two stories today that are different in kind but converging in implication. Jordan, take us through the OpenAI disclosure first.

Jordan: OpenAI published findings that Iran and Russia have been running influence operations using AI-generated personas — fake journalists, fake think tank analysts — to insert content into Western media ecosystems. What's notable is the severity rating. OpenAI rated these campaigns 4 and 5 out of 6. That's the first time they've flagged operations at that impact level. These aren't bot farms posting on social media. These are sophisticated campaigns designed to shape policy narratives, regulatory discourse, and corporate reputation.

Alex: And that's why this is a CISO story, not just a geopolitics story. If state actors can insert AI-generated analysis into the media ecosystem your board reads, your investors read, your regulators read — that's a business risk. Imagine a fabricated think tank report suggesting your company has ties to sanctioned entities, or an AI-generated journalist publishing a story questioning your supply chain integrity. The reputational damage happens before you can even respond.

Jordan: The second AI story is more directly operational. CrowdStrike confirmed that a Chinese-speaking threat actor used an agentic AI pentesting tool called ARTEX alongside Anthropic's Claude to breach South Korean financial institutions. This ran late September through early October and resulted in confirmed data exfiltration. This is one of the first documented cases of agentic AI being used offensively against financial infrastructure.

Alex: Let me be precise about why this matters. It's not that attackers used AI to write a phishing email. It's that they used an agentic tool — meaning the AI was autonomously executing reconnaissance, identifying vulnerabilities, and assisting in exploitation with minimal human direction. That changes the economics of offensive operations. It means a mid-tier threat actor can now punch well above their weight class. Financial services CISOs need to update their threat models to account for AI-augmented adversarial reconnaissance as an active, not theoretical, threat.

Jordan: And the ASOS breach ties into this theme. Attackers compromised Simon AI, an agentic marketing platform integrated with ASOS systems, using stolen employee credentials and MFA bypass. They sent rogue push notifications and accessed customer PII. The vector here wasn't the company's core systems. It was a third-party AI platform with deep integration and broad permissions.

Alex: Every CISO listening should be asking: how many agentic AI platforms have OAuth tokens or API credentials into my environment? What permissions do they have? What's the blast radius if one is compromised? This is the new shadow IT. These tools are being adopted by marketing, sales, customer success — often without security review. Audit your OAuth grants. Today.

Jordan: Let's move to the Atlassian vulnerability because this needs to be actioned immediately. VulnCheck confirmed active exploitation of a critical flaw affecting eight Atlassian products, including Jira and Confluence. These are the backbone of development and IT workflows in most enterprises. If you're running on-prem Atlassian, this is an emergency patch cycle.

Alex: Brief and direct. Check your exposure. Patch now. If you can't patch, implement whatever mitigations Atlassian has published. Confluence in particular has been a recurring target because it's internet-facing in many deployments and contains sensitive internal documentation. Don't wait for your normal patch window on this one.

Jordan: On the governance front, two stories. First, the CUI regulations for federal contractors are nearing finalization. These will impose binding cybersecurity controls and mandatory breach reporting on any contractor handling Controlled Unclassified Information.

Alex: If you're in the defense industrial base or the broader government supply chain, start your gap assessment now. Don't wait for the final rule. The direction is clear: specific security controls, mandatory reporting timelines, and real enforcement. This is CMMC's regulatory cousin, and it's going to have teeth. Budget for it in your next planning cycle.

Jordan: Second, GAO found that federal agencies are lagging on post-quantum cryptography migration. This matters for the private sector because regulatory pressure cascades. When the government can't meet its own timelines, the response is usually to mandate faster action from contractors and regulated industries.

Alex: The harvest-now-decrypt-later threat is real. If you have data with a long sensitivity lifespan — classified information, health records, financial data, intellectual property — and you're not at least inventorying your cryptographic dependencies, you're behind. Start with the inventory. Know where you're using RSA, where you're using elliptic curve, what your certificate lifetimes look like. You don't need to migrate tomorrow, but you need to know the scope of the problem.

Jordan: Now the MonsterCloud story. The DOJ charged Zohar Pinhasi, CEO of a Florida ransomware recovery firm, with wire fraud. He allegedly billed clients over $19 million while secretly paying $8 million to ransomware gangs. The firm claimed to use proprietary decryption technology. It was just paying the ransom and marking up the cost by more than double.

Alex: This is a vendor due diligence story. Every CISO has a ransomware playbook, and many of those playbooks include third-party recovery firms. After this, you need to demand contractual transparency from any IR vendor. Explicit disclosure clauses about whether ransom payments will be made. Audit rights over their remediation methods. And reference checks that go beyond the vendor's marketing materials. The legal exposure here is real. If your organization unknowingly funded a ransom payment through a fraudulent vendor, that creates regulatory, sanctions, and reputational risk.

Jordan: And finally, Australia is weighing mandatory AI incident reporting after an agentic AI attack on its Medicare systems. This is significant because it's one of the first regulatory responses specifically triggered by an agentic AI attack on critical infrastructure.

Alex: Watch this closely. Australia is often a leading indicator for Five Eyes regulatory direction. If mandatory AI incident reporting becomes law there, expect similar frameworks in the UK, Canada, and eventually the US. If you're deploying AI in regulated environments — healthcare, financial services, critical infrastructure — start thinking about what an AI incident reporting obligation would mean for your operations. Build the detection and documentation capability now so you're not scrambling later.

Jordan: Stepping back, Alex, the through-line today is unmistakable. AI has crossed a threshold. We're not talking about theoretical risks anymore. We have documented offensive use against financial institutions. We have agentic platforms being compromised as lateral movement vectors. We have AI-generated personas operating at scale in influence campaigns. And we have governments beginning to regulate specifically in response to agentic AI attacks.

Alex: Agreed. The common thread for CISOs is that AI is simultaneously expanding your attack surface through the agentic tools you're adopting and enhancing the capabilities of your adversaries. Those two trends are compounding. Your 2027 security strategy needs to account for both. And the DNS registry attack reminds us that even the foundational infrastructure we take for granted — DNS, certificate trust, the registry system — can be undermined. Assumptions are liabilities.

Jordan: The board conversation this quarter should include three things: AI as an offensive threat vector, AI platform risk in your own environment, and the regulatory trajectory around AI incident reporting. If your board still thinks AI risk is about bias in chatbots, you're having the wrong conversation.

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

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