Three Stories You Probably Missed: Trump Mobile Leak, FIFA Phishing, and CISA's Supply Chain Cleanup

Let's run through the ones that got buried.

Trump Mobile is leaking customer data. The MVNO — yes, that Trump Mobile — apparently exposed customer information. Details on the exact failure mode here are still thin: whether this was an S3 bucket with a permissive ACL, a misconfigured API endpoint, or something at the carrier layer hasn't been fully confirmed publicly. In practice, MVNOs sit on top of major carrier infrastructure and often handle their own identity and billing stacks with lean engineering teams, which is exactly the environment where IAM hygiene slips. Customers should assume names, contact info, and possibly payment-adjacent data are in the wild.

Phishers are already pre-gaming the 2026 FIFA World Cup. Two years out, and the lure kit is already running. Tournament-themed phishing tends to follow a predictable arc: typosquatted domains, fake ticket purchase flows, credential harvesting dressed up as fan registration. The 2026 tournament spans the US, Canada, and Mexico, which gives attackers three distinct tax and payment system contexts to spoof. One thing the post-mortem will say, when organizations eventually debrief on this, is that nobody flagged the domain registrations early enough. Tools like Google Safe Browsing and Microsoft Defender SmartScreen will catch some of this eventually — emphasis on eventually.

CISA is responding to recent supply chain attacks. The agency confirmed it is actively working through the fallout from upstream software supply chain compromises. The specifics remain vague in public-facing statements, but the pattern is familiar: a trusted build pipeline or third-party package gets poisoned, the artifact propagates into production environments before anyone notices, and now you have a detection and scoping problem that spans dozens of downstream customers. CISA's involvement suggests federal systems are either affected or considered at risk.

Supply chain response at this scale is genuinely hard. You're asking teams to audit every transitive dependency pulled through systems like npm, PyPI, or internal artifact repositories such as AWS CodeArtifact or Azure Artifacts — at speed, under pressure, while production is running.

If you're a platform engineer reading this: check your SBOM tooling is actually generating accurate output, not just producing a document that looks complete.