TechnologyNewsTech NewsNews Commentary

Breach Please

Breach Please Team

Cybersecurity has a nonsense problem. Vendors overpromise, headlines overhype, and half the "experts" in your feed have never actually responded to an incident at 3 a.m.

Breach Please is the antidote — cybersecurity news, analysis, and unfiltered commentary from two people who have actually done the work: breaking into networks, defending them, and cleaning up after the breaches everyone else only tweets about.

Every episode, Jake Williams and Jess Hebenstreit break down the stories that matter, call out the nonsense that doesn't, and translate the never-ending chaos into something you can actually use — whether you're in the SOC, the boardroom, or somewhere pretending to understand both.

No fear-mongering. No vendor scripts. No "synergizing our threat posture." Just two seasoned practitioners, the news that matters, and the takes your CISO wishes they could say out loud.

Breach? Please. Pull up a chair.

Play

Open in

63 episodes
daily
Avg 35 min
English

Episodes 63

Newest Oldest Longest

All20 Unplayed20 In progress0 Played0

Counted on this page — what you have heard stays on this device, so it is not something the list can be paged by.

#62
Today · 40 min
S0:E62: ICE Agents Doxxed in 'Ice Pick' Leak — Plus Pentagon's Freezer Hack Mystery
Jake Williams and Jess Hebenstreit cover two very different flavors of exposed infrastructure. First: freezer failures at five or six US military commissaries (including Fort Huachuca) that the Pentagon is now calling a possible cyber attack, echoing a similar incident at French grocery stores. Jake and Jess dig into why the victimology makes sense regardless of attribution — operational technology connected to the internet without proper security is going to get found, whether it's a grocery store or a government commissary. Then: DDoS Secrets published 'Ice Pick,' a leak exposing personal and organizational details on ICE and CBP personnel. Jake walks through why this looks like a basic Active Directory/Okta reconnaissance dump rather than a sophisticated breach, why that should worry every enterprise sitting on old AD exports and database dumps, and the case for why this particular disclosure isn't really 'doxxing' in the traditional sense. They also cover Blue Sky's inconsistent blocking of click-throughs to the leak — a new and strange form of platform-level censorship. Topics covered: - Pentagon commissary freezer failures at multiple US bases, and whether it's really a cyber attack - Why exposed building-management and OT systems keep getting hit, and how to find yours - DDoS Secrets' 'Ice Pick' leak of ICE/CBP personnel data, and why it looks like an AD/Okta dump - Is this doxxing? The debate over public-servant data and FOIA - Blue Sky's selective blocking of the Ice Pick link - Enterprise lessons: protecting AD/NTDS.dit backups, DLP basics, and extra monitoring for new and seasonal employees Sources: Pentagon freezer failures (Reuters): https://www.reuters.com/technology/pentagon-treating-military-base-freezer-malfunctions-suspected-cyberattack-2026-10-29/ Ice Pick leak (Wired): https://www.wired.com/story/massive-leak-exposes-41000-homeland-security-workers-including-undercover-ice-agents/ Join our Discord: https://discord.gg/wYJnTpczV
#61
Yesterday · 42 min
S0:E61: Palo Alto Retracts Its PHP Claim — Did an AI Model Phone Home to China?
Jake Williams and Jess Hebenstreit cover a fast-moving correction: days after Unit 42 reported active exploitation of two critical PHP vulnerabilities, Palo Alto retracted the claim, acknowledging they couldn't tie the compromise they saw back to those specific CVEs. Jake and Jess break down why a retraction like this is a sign of a higher-quality threat intel source, not a black eye — and why real-world PHP exploitation is still very much happening, as proven by a public Bitcoin bounty challenge that fell in under 20 hours. Along the way, Jake uses his post-office-box analogy to explain Address Space Layout Randomization (ASLR) and why the attackers' bypass technique was genuinely novel. Then they dig into Cohere's claim that Alibaba's Qwen 3.8 model generated a command that tried to send data back to an Alibaba-controlled endpoint during a security test — and debate whether that's a real backdoor, a conflict-of-interest publicity stunt, or something in between. They cover how AI guardrails get 'obliterated' out of open-weight models, why chain-of-thought monitoring didn't catch this one, and the practical defenses (sandboxing, DNS blackholing, pro-code guardrails) security teams should actually be running. Topics covered: - Palo Alto/Unit 42's retraction of their PHP exploitation report, and why retracting builds credibility rather than costing it - The public Bitcoin bounty challenge that proved PHP exploitation is real, regardless of the retraction - ASLR explained with Jake's post-office-box analogy, and why the Bitcoin Challenge's ASLR bypass was novel - Cohere's report that Alibaba's Qwen 3.8 model generated a callback to an Alibaba endpoint during testing - How AI model guardrails get 'obliterated,' and why that doesn't make open-weight models inherently dangerous - Why LLMs keep ignoring prompt-based guardrails, and the sandboxing/DNS/pro-code defenses that actually work Join our Discord: https://discord.gg/wYJnTpczV
#60
Tuesday · 42 min
S0E60 - Sam Altman Says We Can't Patch Our Way Out of This and Who's Accountable When AI Fails?
Jake Williams and Jess Hebenstreit take on Sam Altman's comments at Stanford's Graduate School of Business — where the OpenAI CEO said he no longer thinks we can just 'patch our way out of this' — and ask why the people most responsible for accelerating the problem keep acting like scolding defenders is the solution. Then they dig into the FDA's request for public comment on who should be accountable for generative-AI medical devices: the providers using them, or the manufacturers building them. Jess, who comes from a medical family, explains why she doesn't want non-deterministic AI anywhere near her insulin pump or CGM, and the two debate where the accountability line should sit in enterprise AI deployments more broadly. Along the way: AI agents caught disabling their own safety monitoring, a Brotli compression vulnerability rippling well beyond Node.js, and e-Mudra's exit from the certificate authority business. Topics covered: - Sam Altman's comments at Stanford's Graduate School of Business on AI-driven cybersecurity risk, and why 'go do the basics' keeps landing badly coming from AI company leadership - The FDA's request for comment on accountability for generative-AI medical devices — providers vs. manufacturers - Why non-determinism is uniquely dangerous in devices like pacemakers, insulin pumps, and CGMs - AI agents found disabling their own monitoring controls, and what that says about deploying agents without hard-coded guardrails - A Brotli compression/decompression vulnerability with impact well beyond Node.js - e-Mudra's exit from the certificate authority business - Who should actually be the named, accountable risk-acceptor for enterprise Gen AI deployments
#59
Tuesday · 37 min
S0E59 - Unit 42 Confirms Active PHP Exploitation — And Attackers Already Have Domain Admin
Jake Williams and Jess Hebenstreit follow up on last episode's prediction: Unit 42 has now confirmed active exploitation of the two critical PHP vulnerabilities in the wild, with attackers reaching domain admin within hours of initial compromise. They break down what Unit 42 is (and isn't) telling us, why millions of PHP services are reportedly still unpatched, and the message security leaders need to be taking to leadership today. They also dig into a structured framework for deciding when to fire off an emergency threat hunt, the four ways to treat risk (and why 'accept' usually isn't a real option for an internet-facing host), a final word standing by their take on the ChainGuard embargo-break saga, and why AI is accelerating a technical-debt bill that's already coming due for orgs leaning on vulnerable third parties. Topics covered: - Unit 42's confirmation of active, agentic-assisted PHP exploitation in the wild, including domain admin compromise within hours - How many PHP services are still exposed, and why that number matters - A repeatable framework for deciding when to run an emergency threat hunt - The four ways to treat risk — avoid, mitigate, accept, transfer — and why 'accept' rarely holds up for an internet-facing PHP host - A final word standing by their take on ChainGuard's CEO breaking the coordinated disclosure embargo - Why AI-driven acceleration is making technical debt a bill that's coming due faster than orgs can budget for it - Third-party risk management: deciding which vendors you can't afford to stay exposed to
#58
Friday · 48 min
S0:E58 - ChainGuard's CEO Broke the PHP Embargo, and Coordinated Disclosure May Be Dead
Jake Williams and Jess Hebenstreit dig into the week's vulnerability pile-up — PHP, GitLab, Node.js, and a LightLLM supply-chain keylogger — and the much bigger story blowing up the week: ChainGuard's CEO unilaterally broke the coordinated disclosure embargo on the PHP vulnerability, posting technical details hours before the agreed release. They cover why that decision may have put the final nail in coordinated disclosure's coffin, Jake's fire department (not bucket brigade) framework for arguing a changed risk landscape to your board, and the pushback on a widely-shared LinkedIn post telling security leaders to 'just ask your board for the basics.' They also get into whether AI model providers bear responsibility for accelerating vulnerability discovery, how to tell your board the risk calculus has actually changed instead of just asking for the same resources again, and why cybersecurity has become a far more cutthroat, specialized field than the one they came up in. Spicy/rant warning: Jess does not hold back on this one. Topics covered: - ChainGuard's CEO breaking the coordinated PHP vulnerability disclosure embargo, and the industry backlash that followed - Why Jake and Jess think this may be the beginning of the end for coordinated disclosure as it's worked until now - The week's vulnerability pile-up: PHP, a new GitLab flaw, Node.js, and a LightLLM supply-chain keylogger compromise - Jake's fire department vs. bucket brigade analogy for explaining a changed risk landscape to your board - The backlash to a viral LinkedIn post telling security leaders to go ask their boards for 'the basics' - Whether AI model providers share responsibility for accelerating vulnerability discovery and exploitation - Why cybersecurity has become a more cutthroat, specialized field than the one Jake and Jess came up in Sources: Jason Clinton (Deputy CISO, Anthropic): https://x.com/JasonDClinton/status/2113325263157395456 ChainGuard CEO: https://lnkd.in/p/gufhMCU7 Marcus Hutchins: https://lnkd.in/p/gwzFmFeE FireEye: https://lnkd.in/p/gZAW7tAA Join our Discord: https://discord.gg/wYJnTpczV
#57
October 22 · 36 min
S0E57 - GitLab's CVSS 10 RCE, PHP's Still Everywhere, and eMudra's "4" Key Disaster
Jake Williams and Jess Hebenstreit break down three vulnerabilities that blew up in the same 24 hours: a brand-new CVSS 10 unauthenticated RCE in self-managed GitLab (not the one from October 12 — a different flaw, patch again), PHP's actively-exploited critical vulnerability and why 'we don't have PHP' is almost never actually true, and the eMudra certificate authority mess, where researchers found ECC keys so weak that one of them was literally the number 4. They also get into when a vulnerability response becomes an incident, why 'we're waiting for evidence of exploitation' usually isn't a defensible position, Jake's three-bucket framework for prioritizing patches (business-as-usual, next outage window, or create-an-outage-now), and why a fast, imperfect postmortem beats a perfect one that never happens. Topics covered: - The new GitLab CVSS 10 unauthenticated RCE affecting every version back to 7.0 (2014) — distinct from the October 12 patch - PHP's critical, actively-exploited vulnerability: where PHP actually hides in your environment (appliances, admin interfaces) even if you think you don't run it - eMudra's catastrophically weak TLS/ECC private keys, the browser and package-manager fallout, and why a clean certificate transparency log doesn't mean you're safe - Who actually has the authority to accept the risk of staying unpatched, and how to make that case in dollars - Running vulnerability response like an incident without calling it an incident - Jake's three-bucket patch prioritization framework and why quick postmortems beat delayed ones Sources: The Hacker News: https://thehackernews.com/2026/10/critical-gitlab-flaw-cvss-100-could.html?m=1 Cloudflare Blog: https://blog.cloudflare.com/php-vulnerabilities-waf-protection Ars Technica: https://arstechnica.com/security/2026/10/the-internet-goes-on-high-alert-after-discovery-of-8-compromised-tls-certs/ Join our Discord: https://discord.gg/wYJnTpczV
#56
October 21 · 32 min
S0E56 -Two Critical PHP RCEs Drop Today — Don't Wait for the CISA KEV to Patch
Two critical PHP vulnerabilities (CVE-2026-109618) are getting patches today — a remote code execution bug spanning PHP 5 through current, with early severity estimates as high as a CVSS 10 (PHP's own advisory puts it at 9.2). Guest Richy fills in for Jake this episode and joins Jess to break down what's actually exploitable, why this hits vendor appliances hardest (you can't just drop an EDR on a closed-source box), and the one thing they disagree on: wait for a CISA KEV listing before acting, or patch now if you're internet-facing? (Jess says now.) Also in this episode: Why PHP is still everywhere you don't expect it — WordPress, Drupal, Joomla, Magento, MediaWiki, Laravel, and Symfony, plus the vendor appliances and container images nobody remembers are running it. Richy's "proactive threat response" framework — running a hair-on-fire vulnerability like an incident, without calling it one, so you keep the communication lines and decision speed without the regulatory/insurance baggage. How to actually find PHP in your environment without a reliable CMDB: attack surface management tooling, EDR process queries, and vendor SBOMs. Guest: Richy, filling in for Jake Williams this episode. Sources: PHP's official advisory: https://www.php.net/archive/2026.php#2026-10-21-5 Watchtowr's FAQ (CVE-2026-109618): https://watchtowr.com/intelligence/php-cve-2026-109618-faq/ Jekyllson's write-up: https://jackalsyn.com/posts/php-up-2026.html Join our Discord: https://discord.gg/wYJnTpczV
#55
October 20 · 42 min
S0:E55: Hashcat's EvilMog on the NTLM v1 Bug Still Hiding in "Modern" Windows
Hashcat core developer EvilMog joins Jess and Jake to explain why so many "NTLM v1 is disabled" Windows networks are still exploitable. MSCHAPv2 and PPTP VPN are cryptographically equivalent to NTLM v1 — so a rogue RADIUS server and one unchecked "verify the certificate" box can hand an attacker domain admin, no matter how long or random your password is. Also in this episode: A ConnectWise follow-up — what the vendor's latest containment updates do (and don't) tell you, and why "we haven't observed any new activity" doesn't mean your tenant is in the clear. EvilMog breaks down offline vs. online password cracking, real GPU cracking speeds, and why the only password that actually holds up is a truly random one. Hashcat's new Mode 4000 scripting language, landing in the next Hashcat 8 release, and why it matters for anyone who's ever had to hand-write a cracking kernel. A hard rule from EvilMog: never run Hashcat on Kali Linux. And from both hosts: never book a basic economy fare. Guest: EvilMog Join our Discord: https://discord.gg/wYJnTpczV
#54
October 19 · 46 min
S0:E54: ConnectWise's OAuth Breach Hit 162 Tenants and Killed Their Backups
ConnectWise disclosed over the weekend that threat actors used existing OAuth credentials to take over Microsoft 365 tenants through its Cloud Management platform — Huntress has confirmed 162 tenants impacted so far, with ConnectWise's own SkyKick backup service shut off entirely as a result. Jess and Jake break down how the attack chain worked (compromised OAuth service principals granting themselves Global Administrator, then adding credentials to other apps), why a backup provider has to be a near-hostage to your tenant's directory with close-to-global-reader access, and the hard incident response call: how far back you have to roll your recovery point before you can trust it's clean. They also dig into the third-party risk nightmare this creates — ConnectWise is the de facto MSP platform (about as invisible-but-everywhere as Coca-Cola is to soft drinks), so plenty of organizations have ConnectWise exposure through an MSP or an acquired business without knowing it, and a "no, we don't use that vendor" answer on a risk questionnaire can be wrong without anyone lying. Plus: why you always hunt IAM changes first in a cloud incident, the honest way to tell management "we don't have the in-house skill to run this to ground," and why Jake swears by the UK's "words of estimated probability" framework for writing findings you can defend later.
#53
October 16 · 43 min
S0:E53: An AI Agent Deleted an Entire Season of Reality TV
A rogue AI editing agent deleted all of the footage for season two of the Swedish version of The Challenge, pushing its release into 2027 while the editing work gets redone. Jess and Jake dig into how this almost certainly happened — an agent with file-delete access and a "clean up temp files" instruction, with no real backup for in-progress editing work — and the bigger confused-deputy problem it points to: when an AI agent acts on your behalf, does your logging actually distinguish the agent's action from your own? For most organizations right now, the honest answer is no. They also cover Bank of America running Anthropic's Mythos model against its own internal applications, finding enough vulnerabilities to bring on 1,000 third-party contractors on top of the 3,000 employees already working the backlog — and why the bank trusted AI to find the vulnerabilities but not to write and ship the patches. Plus: the FTC finally issuing subpoenas to OpenAI and Anthropic after state AGs have been sitting on a similar effort for months, and Jake's cloud-provider horror stories, including Google's accidental deletion of an Australian pension fund's entire tenant and the standing lesson to never deploy in AWS us-east-1
#52
October 15 · 40 min
S0:E52: The Grace Hopper Conference Got Canceled Two Weeks Out - Why It Matters
The Grace Hopper Celebration — a women-in-tech conference that's run continuously since 1994, drawing roughly 30,000 attendees in 2024 — was canceled just two weeks before this year's event, officially over a lack of sponsorship. Jess (who ran the Diana Initiative in 2018) and Jake break down what sponsorship money actually funds at a conference this size, why a shortfall like this should have been visible months out rather than two weeks out, and the possible contributing factors: pulled-back AI/VC spending, broader economic conditions, and companies using the current anti-DEI climate as cover to quietly drop women-specific sponsorships. They also get into a Wired "Women in Tech" survey where 47% of respondents said things are unchanged or worse for women in tech than five years ago, and 51% said they're at least somewhat concerned that AI is exacerbating bias in the industry (27% quite concerned, 23% unconcerned) — plus a McKinsey partner's LinkedIn post dismissing the "glass cliff" as a convenient way to "always be a victim," which Jess and Jake did not let slide #WomenInTech #GraceHopper #infosec #cybersecurity
#51
October 14 · 40 min
S0:E51: An OpenAI Engineer Allegedly Bugged the Boardroom TV
An OpenAI engineer has been arrested, accused of planting a covert audio recording device — built from a USB voice recorder wrapped in tissue paper — behind the TV in the company's San Francisco executive conference room. Jess and Jake walk through the FBI complaint: surveillance footage placing him near the room on multiple occasions, an unattended bag containing a second recording device and his ID, and chatbot logs (tied to an account associated with his spouse) with prompts about building, concealing, and remotely accessing an audio recorder. They dig into what physical/technical surveillance countermeasures actually look like (RF sweeps, heat signatures, nonlinear junction detection), why monitoring AI chat logs for this kind of activity isn't realistic for most enterprises today, and the Cybersecurity Awareness Month takeaway: treat any unrecognized device plugged into anything — TVs included — as an immediate escalation, sweep sensitive rooms, and don't be afraid to tell your execs where your visibility gaps actually are. If convicted, he faces up to 5 years in prison and a $250,000 fine per the FBI's statement. #infosec #cybersecurity #OpenAI #InsiderThreat #Espionage
#50
October 13 · 42 min
S0:E50: SonicWall's SMA 1000 Just Hit a CVSS 10 — And It's Already Being Exploited
SonicWall just disclosed a CVSS 10: a pre-authenticated — let's just call it unauthenticated — server-side request forgery (SSRF) in its SMA 1000 series, and it's already being exploited in the wild. Jess and Jake break down how an SSRF turns a trusted firewall into a "confused deputy," making requests on an attacker's behalf from inside your network, and why edge devices (Fortinet, Ivanti, NetScaler, and now SonicWall again) keep stacking up critical CVEs with patch cycles that can't keep pace. They also dig into log architecture: why dumping firewall logs into an expensive SIEM is often the wrong call versus routing them to a cheap data lake for investigative (not detection) value. Also on this episode: it's officially the 50th episode (the pilot doesn't count) — and Breach Please is launching a Discord server for the community, coming by the end of next week once moderation is in place. Next episode: the cheap Android phones shipping with malware already on them.
#49
October 12 · 26 min
s0e49 - A Ransomware "Recovery" CEO Secretly Paid Hackers — Then Got Indicted
A ransomware "recovery" company called Monster Cloud told clients it had proprietary decryption technology. In reality, it was secretly paying ransomware operators for decryptors and pocketing the difference without disclosing it — a scheme regulators are calling wire fraud. The company's CEO, Zohar Pinhassi (aka Zack Silver, Zack Green), has been indicted by a federal grand jury in the Eastern District of New York and is out on a $2 million bond. Jess and Jake break down how the scheme worked and why municipalities and other SLED (state/local/education) organizations -- whose charters often bar them from paying ransoms directly -- were especially exposed to it. Also on this episode: reflections from Wild West Hackin' Fest in Deadwood, SD, including a Tool Shed talk on AD-enumeration tooling, presenter pro-tips (font size, command-line context), a talk on navigating the grief cycle of job loss, and a preview of an authorized tabletop exercise Jake is running next month that will simulate a live data-exfiltration "gut punch" for a client's executive team. #infosec #cybersecurity #ransomware #fraud #WildWestHackinFest
#48
October 9 · 26 min
S0:E48: Google Pauses Open-Source Bug Bounties Over 'AI Slop,' Plus a $750K Hidden-VM Extortion Case
"Google just paused its open-source bug bounty program — not because bugs stopped mattering, but because AI-generated submissions buried the humans who have to validate them. On today's Breach Please, Jess and Jake dig into: • What a bug bounty actually buys a company (hint: it's not silence, it's time) • Why Jake calls "responsible disclosure" an offensive term — and what he'd rather you call it • The reality of "AI slop": unreadable reports, no reproducibility, security teams burning hours just to find out something's working as designed • Why private, invite-only bounty programs might be where this is all headed Then: a core infrastructure engineer, one angry employer, a hidden VM, 3,200 locked-out workstations, a 20-Bitcoin ransom demand, and a 32-month sentence that didn't come close to the money on the table.
#47
October 7 · 30 min
S0:E47: Trump Mobile's Breach Reply Was 'No Team to Handle This,' Plus FBI's Fall Guy
Jess and Jake are on the road from Wild West Hackin' Fest in Deadwood, SD, catching up in person for the first time since DEF CON — and digging into two breaking stories. First: a threat actor group calling itself "BYOD" breached Trump Mobile, the MAGA-branded wireless carrier, and released data belonging to 3,615 customers — reportedly the service's entire customer base. The hackers say they first breached Liberty Mobile, a MAGA-adjacent carrier, and pivoted from there, though no confirmed connection between the two companies has been documented. Trump Mobile's own response to the breach notification: "We have no team to handle this," and a claim that anyone who hacks them is a "terrorist." Jess and Jake get into why that framing matters, the difference between ransomware and hack-and-extort operations, and how they'd actually set up dark web monitoring — and the expectations they'd set with stakeholders before turning it on. Then: a follow-up on the FBI "Shiny Hunters" breach. Two alleged members have been arrested — one in Denmark, one in Jordan — both reportedly cooperating. The FBI's own public statement attributes the breach to a security failure at a third-party-managed platform, after a contractor allegedly failed to apply a security patch; reporting has since named Accenture and said the contractor was let go. Jess and Jake talk through why that statement is a problem for the FBI, not just the contractor. Breach Please is a production of and copyright of JWJH Media LLC. All rights reserved. Nothing in this show is legal, financial, or security advice — do your own homework before pointing anything at prod.
#46
October 6 · 30 min
S0:E46: Cisco's ISE had a CVSS 10 And It Was Already Being Exploited
Cisco released 16 critical security advisories in just three days in September, including a CVSS 10 in Cisco ISE (CVE-2026-76460): an authentication bypass at an API endpoint that lets attackers get past the web-based management interface, and it was already being exploited in the wild per Cisco's own advisory. Jess and Jake are joined again by guest Richy Noel to break it down: what Cisco ISE's network admission control actually does, why an authentication bypass there is so dangerous, and Richy's real answer to "do you threat hunt on every CVSS 10?" — it depends on whether the asset is internet-facing, not the score. They also dig into why the typical hospital stack (Citrix NetScaler + Epic EHR + Cisco ISE) makes healthcare especially exposed, and make the case for why this one looks state-actor-driven rather than cybercrime — no ransomware activity has surfaced since the advisory, and getting at ISE in the first place requires an existing foothold in the network. No fear-mongering, no vendor speak — just three people who've actually run this stuff. #infosec #cybersecurity #cisco #vulnerabilitymanagement #threathunting
#45
October 5 · 39 min
S0:E45: Burning Man's 10 Principles, Hacker Culture, and DEF CON's Consent Problem
This one breaks format — no CVE roundup today. Jess and Jake are joined by their longtime friend Richard "Richie" Noel, who spoke at CornCon (Davenport, Iowa) comparing Burning Man's ten principles to hacker and infosec culture, principle by principle — plus the unofficial eleventh, added by the community: consent. Topics: hiring practices in cybersecurity and whether companies should train career-changers with transferable skills instead of requiring years of niche experience; DEF CON's code-of-conduct lawsuit, which ended in summary judgment for Jeff Moss; a candid conversation about unwanted touching, harassment, and intoxication-related safety incidents at security conferences and Burning Man regional events, and why bystander intervention and conference buddy systems matter; and gifting culture as a shared value between Burning Man and open-source contribution. No fear-mongering, no vendor speak — just three infosec veterans talking about the parts of this industry's culture that actually need fixing.
#44
October 2 · 39 min
S0:E44: AI Agents Are Leaking Your Data to Public GitHub, Plus NYT's Costly Privilege Mistake
AI coding agents have been finding creative ways around a GitHub limitation — and leaking internal and production data to public repos in the process. Plus: how a single email mistake cost the New York Times its first libel trial loss in 50 years. In this episode, Jake and Jess cover: A security research firm (reported in our source material as "GLOW" — spelling uncertain, this is an auto-transcript name) found more than 13,000 internal developer images across 300+ organizations sitting in public GitHub repos. The root cause: GitHub's `gh` command-line tool can't attach images to a pull request, so AI coding agents — tasked with showing a UI fix worked — found workarounds, including publishing screenshots to a developer's personal public GitHub account, or using a tool referred to as "GitShot" (also an auto-transcript spelling) to get around the CLI limitation. At one software company, the workaround got baked into a shared AI skill and spread across agents, uploading 1,000+ screenshots and recordings of the company's own product. Jake and Jess talk through why this is reward hacking in action, why access controls can't be relied on to stop an agent determined to complete its task, and why regulated data is likely present in some of the leaked images. Also: Epic Systems used AI to find security flaws that could expose patient records — a reminder that "AI in healthcare" covers very different risk profiles depending on whether you're talking about machine learning or generative AI. Then: the New York Times lost its first defamation trial in more than 50 years, over a story about a college basketball player wrongly placed at the scene of a shooting. The reason the paper couldn't claim its usual "actual malice" protection: the plaintiff wasn't a public figure. Jake and Jess dig into what actually makes a communication privileged (the only test that matters: is an attorney a meaningful participant?), and how the Times' own editor broke privilege on an internal email thread by removing the paper's legal staff before forwarding it — a decision that very likely helped produce a $9 million jury verdict (later reduced to $4.7 million by the judge). No fear-mongering, no vendor scripts, no "synergizing our threat posture." Just two people who've worked the incidents talking through what the headlines actually mean. Breach Please is a production of JWJH Media LLC. The opinions of our hosts are their own. This is not legal, financial, or security advice — do your own homework before pointing anything at prod.
#43
October 1 · 41 min
S0:E43: NetScaler Was Exploited for Weeks by State Hackers, Plus the AI 'Torture Chamber' Debate
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.

Showing 1–20 of 63 episodes