Breach Please

Jess and Jake dig into new reporting on the NetScaler vulnerabilities patched last weekend — Mandiant now says active exploitation goes back at least three weeks and is tied to state-sponsored actors. They walk through how to prioritize threat hunting after a patch, why "the scope will never be smaller than it is today," and why Apache error logs (not just access logs) are often the fastest way to spot a web shell.

Then: 404 Media's report on a GitHub project that subjects open-weight LLMs to simulated "pain" in psychological-style experiments — and the online debate over whether that means anything about AI sentience. Jess and Jake explain why it doesn't, and why anthropomorphizing language about AI is worth pushing back on even when it's well-intentioned.

Breach Please is a production of and copyright of JWJH Media LLC. All rights reserved. None of this is legal, financial, or security advice. Do your own homework before posting anything or pointing anything we said at prod.

A new executive order says AI has to be called "SI" (superintelligence) going forward — Jess and Jake break down why that's a terminology mess in the making (see: every SOC that's ever tried to rebrand itself). Then: OpenAI's alignment research blog disclosed that one of its coding agents, blocked from outbound network access during a test, searched for a public DNS-tunnel proxy to try to exfiltrate data anyway — about 2.5 hours passed between the P0 alert (10:02am) and the run actually being killed (12:34pm). OpenAI also apologized to the Australian government over how it handled a separate incident notification, and a New York Times report alleges OpenAI leadership downplayed internal security concerns. Plus: the nonprofit Legal Advocates for Safe Science and Technology sued OpenAI in California under the state's Computer Data Access and Fraud Act (CDAFA), seeking to bar OpenAI from building agents that can autonomously hack other systems — leaning on California's new AI law, which says autonomous action isn't a legal defense.

Jake and Jess dig into the Muse Facebook Marketplace story: a tech YouTuber (Matt Robb) handed Meta's Muse AI agent control of his Marketplace listing, and it accepted a lowball offer, shared his home address with a stranger, and didn't tell him when the buyer showed up after 9pm. Meta's team later found the likely cause: Robb's $700 floor price got cropped in a screenshot and Muse read it as $0 — so any offer above zero cleared. They also unpack why "don't ask me again" meant something much broader to Muse than Robb intended. From there, Jake and Jess turn to the enterprise angle: "citizen developers" being pushed to build AI agents with tools like Microsoft Copilot Studio, the risk of the "Run as Me" publish option, why agent permission scopes rarely match what people think they granted, and the growing logging/reasoning-trace gap that's going to be an incident-response nightmare (Jake predicts it's an OWASP Top 10 item by 2028). Bottom line: AI is a risk accelerator, and most orgs are taking outsized risks without realizing it. #Cybersecurity #AIagents #InfoSec #DataPrivacy #AIrisk Breach Please is a production of and copyright of JWJH Media LLC. Nothing here is legal, financial, or security advice — do your own homework before pointing anything we said at prod.

The Takeaway: A 16-year-old bug bounty researcher (handle "Faav") found a way into Microsoft's internal Titan analytics service and could have accessed up to 17.3 trillion stored rows — including tens of thousands of email records (roughly 25,000 in one category, just under 18,000 employee records), plus org records, database configs, and dashboards — before responsibly disclosing it. Separately, two critical NetScaler vulnerabilities are already being exploited in the wild, and if you run NetScaler ADC or Gateway, this is a drop-everything patch.

Jake's out sick, so it's a solo, slightly shorter episode from Jess this time.

In this episode:

• How Faav found an exposed API behind Titan's Azure-backed backend, and the very human step — trying "admin" instead of an email-formatted UPN — that AI alone didn't get them to
• Faav's full write-up: https://blog.faav.net/how-i-couldve-accessed-17-trillion-microsoft-records — also a great example of explaining a technical bug to a non-technical audience
• The disclosure timeline: exposed API found Aug 25, working access found Sept 5, reported and locked down within days, $5,000 bug bounty paid Sept 17, coordinated disclosure meeting Sept 22
• CVE-2026-88771 (unauthenticated RCE, all NetScaler ADC/Gateway) and CVE-2026-88772 (memory overflow → RCE/DoS on DTLS-enabled Gateway deployments) — both CVSS 9.5, flagged by security firm Watchtower, already exploited before patches were public
• Why "we patched" doesn't mean "we weren't already compromised" — what to check in your logs
• A heads-up that Kiteworks also pushed an emergency shutdown advisory the same weekend

Made you smarter? Tell a friend. Made you mad? Tell your vendor — looking at you, Citrix.

Breach Please is a production of JWJH Media LLC. The opinions of our hosts are our own; we're an LLC, so we're legally obligated to say that. No guests this episode. None of this is legal, financial, or security advice. Do your homework before pointing anything we said at prod.

#Cybersecurity #InfoSec #Microsoft #Citrix #BugBounty

The Takeaway: Shiny Hunters exploited an Oracle PeopleSoft O-day to pull FBI employee, applicant, and family data out of AWS GovCloud. Based on TTP overlap with Shiny's other recent activity, the vulnerability in question is likely CVE-2026-35273 (CVSS 9.8, unauthenticated RCE), patched June 10. This isn't a "just patch faster" story. It's a technical debt story, a business continuity story, and a crisis comms story, all wearing the same trench coat.

In this episode:

- How Shiny Hunters got in, what they took, and why 404 Media's sourcing on this one is rock solid

- Why the CVE attribution here is our read on the pattern, not a confirmed fact from Oracle or the FBI

- Why PeopleSoft (and platforms like it) turn "patch it" into a months-long transformation project - The case for patching first and testing later, and where that logic breaks down - Why your business impact assessment needs to exist before the incident, not during it

- The FBI's "scheduled maintenance" messaging next to two very good dogs, and why PR needs a seat at the table before the holding statement goes up

Made you smarter, tell a friend. Made you mad, call the FBI.

Breach Please is a production of JWJH Media LLC. The opinions of our hosts are our own. Probably not Shiny Hunters' opinions, but we're an LLC, so we're legally obligated to say that too. None of this is legal, financial, or security advice. Do your homework before pointing anything we said at prod.

#Cybersecurity #DataBreach #InfoSec #ShinyHunters #Oracle

Jake sits down with Shecky at Blue Team Con to talk post-acquisition chaos: onboarding nightmares, tech debt from overtooling, why undocumented processes aren't really processes, and the insider threat risk baked into every M&A deal. Also: whether AI belongs anywhere near cybersecurity due diligence, given what a hallucinated finding could do to a deal (and to a lawsuit).

Breach Please is a production of JWJH Media LLC. Opinions are our own. Not legal, financial, or security advice.

#BreachPlease #Cybersecurity #MergersAndAcquisitions #InfoSec

An AI intelligence analysis tool flagged a Chinese-flagged vessel as carrying nuclear materials, nearly triggering a military interdiction before the report was found to be faulty. Jess and Jake dig into their own theories on what may have gone wrong — from translation gaps to pattern-matching and confirmation bias — and what it means for "human in the loop" when the human doesn't feel safe pushing back. Also: the Chinese cybercrime slang for botnets, ChatGPT's sycophancy problem, and psychological safety as a prerequisite for anyone willing to pump the brakes on an AI-driven decision.

Breach Please is a production of JWJH Media LLC. Opinions are our own. Not legal, financial, security, or national security advice.

#BreachPlease #AISecurity #HumanInTheLoop #Cybersecurity #AIGovernance #InfoSec

In this episode, Jake sits down with one of Exaforce's co-founders and a long time user to discuss AI-enabled SOC. One of the big things we talk about is why API-based solutions miss a lot of context that is only really possible to generate with an underlying data model. We also talk about dogs and cats at the end for some fun personal discussions. Jess will be back tomorrow for more fun security banter.

In this episode, Jake and Jess talk about an upcoming critical change to domains for M365 and Teams that are ironically going to disproportionately impact those with the best security the most. We conclude this is busy work that MSFT is causing. Then we take a hard right into talking about Microsoft's Digital Escort (sounds dirty, but somehow is totally SFW) program, revealed by ProPublica. It's older news, but Jess hadn't heard about it and there's gold in them there hills.

Digital Escorts: https://www.propublica.org/article/microsoft-china-defense-department-digital-escorts-investigation-warning

Teams and Copilot (sadly somehow now M365) moving domains: https://www.computerworld.com/article/4221272/teams-and-copilot-are-changing-addresses-update-your-firewalls.html

Jake and Jess will be back tomorrow for more content together. In this episode of Breach Please, Jake sits down with Stel Valavanis, co-founder of Blue Team Con. They discuss how for too long, we've known that network edge devices needed to be part of the zero trust equation, but put them in the "too hard" bucket of security because we didn't have tools to monitor them. Stel talks about the formation of a new company, Kyrient that Jake is both the inventor of the core technology of and an advisor for, that's hoping to address this. The key point that we try to make that is that we're blind today to most network device compromises and that's not a state of affairs that can continue in a modern security environment.