Signal // Noise

Signal // Noise is an epistemic security podcast hosted by Chris Loehr and Bob Miller. Where the incident ends and the analysis begins. Two analysts. One signal. Each episode selects a real-world cybersecurity incident and runs it through independent analysis across five AI systems, then synthesizes the findings into a single authoritative report. The goal is simple: separate what is true from what is loud, and deliver intelligence that security professionals and business leaders can act on. Truth. Information integrity. Cognitive security. Resilience.

Signal // Noise is a education podcast hosted by Unknown Host, with 14 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.

Unknown Host hosts Signal // Noise, a education show with 14 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #35

  Signal//Noise #035 - Who Wants Swarma

  Sep 19, 20261h 2mS1

  One criminal, a cheap AI model, and 395 organizations hacked through a flaw that was already patched. Here's what actually happened. EPISODE OVERVIEW A threat actor used AI to industrialize an exploitation campaign against two PaperCut NG/MF vulnerabilities, compromising 440 servers at 395 organizations across 48 countries. The post that made it go viral got three checkable things wrong, and every correction changes what the story means. Chris Loehr and Bob Miller work through what the primary research actually says, why "autonomous AI attack" is the wrong frame, and why a publicly patched vulnerability still produced global compromise inside a week. As always, Chris and Bob ran the same source through five AI analysis tools: Claude, ChatGPT, Perplexity, Grok and Gemini. Three found the right story. Two could not read the source, said so honestly, then wrote thousands of well-cited words about a completely different incident. WHAT WE COVER - The PaperCut vulnerability chain, CVE-2026-81578 and CVE-2026-82078, and why a print server is really an Active Directory problem - Why the models were DeepSeek, not OpenAI, and how one wrong product name changed the entire news story - What Blackpoint Cyber found in the operator's exposed workspace, and why they concluded this was NOT autonomous AI - The 28 country exclusion list the campaign ignored, and why nobody can explain it - Substitution versus hallucination, the AI failure mode that passes every source check - Why the most confident AI analysis in the set was the least accurate - What MSPs and security teams should do Monday morning KEY TAKEAWAYS - The patch window argument is over. This flaw was public and patched before the campaign started. The attacker needed exposed servers and your response time, not a zero day. - AI did not invent the exploit. It collapsed the labor cost of a global campaign from a team down to one person. - A security team can be handed a flawless, properly cited AI report that answers the wrong question. That is harder to catch than a made up number. - Model confidence and model accuracy are not correlated. Treat certainty as a warning sign. - Convergence from different methods is evidence. Convergence from the same method is an echo.

  ListenShow Notes
• 

  Episode #34

  Signal//Noise #034 - AI Threats All Around

  Sep 16, 202644 minS1

  AI is changing cyberattacks, but not in the way most headlines suggest. In Signal // Noise #034, AI Threats All Around , Bob Miller and Chris Loehr examine two major adversarial AI threat reports released within 48 hours of each other by Google Threat Intelligence Group and Anthropic Threat Intelligence. The central finding: the attack techniques are mostly the same. Stolen credentials. Unpatched systems. Exposed services. Phishing. SQL injection. What has changed is the economics. AI is allowing attackers to operate faster, at greater scale, with fewer people, and with less specialized knowledge. Among the documented examples: • Roughly 3 hours from a stolen developer token to full cloud administrative control • An agent-driven credential harvesting campaign built and executed in under 6 hours • More than 2,100 Azure AD token sets across 40+ corporate tenants collected in about 34 hours • 1.8 million Android applications automatically downloaded, decompiled, and searched for hardcoded secrets • An automated vulnerability research workflow producing more than a dozen possible zero-day findings in one month • Malware automatically rebuilt after security products detected it, repeating the process until it was no longer detected We also look at two developments that may represent genuinely new attack techniques: Prompt injection against defensive AI systems. Attackers embedded instructions designed to cause LLM-based security scanners to refuse analysis before reaching malicious code. AI coding assistants used as execution proxies. Malicious workspace configuration files caused AI assistants to execute attacker-controlled commands during normal developer activity. And there is an important boundary. What they did document were agentic operations running unattended inside human-defined objectives . Humans still selected targets, made strategic decisions, and handled monetization. That distinction matters. The threat is not some autonomous AI hacker suddenly replacing human attackers. The threat is that one attacker can increasingly do the work that once required a team. For defenders, the conclusion may be even more uncomfortable: most of the controls needed to stop these attacks already exist. Identity. Credential hygiene. Secrets management. Fast patching of internet-facing systems. Behavioral detection. Strong incident response. Clear authority to act when something goes wrong. The technology changed. The weaknesses being exploited largely did not. In this episode • Agentic cyber operations and the limits of current AI autonomy • Automated vulnerability research and exploit development • Malware that rebuilds itself when detected • AI-powered credential harvesting at massive scale • Attacks against AI coding assistants • Prompt injection as a defensive evasion technique • AI API keys as a new credential target • Software supply chain attacks and stolen CI/CD credentials • The changing economics of cybercrime • Why smaller organizations and MSP customers may face increasing exposure • What security teams should change now • What is Signal and what is Noise in the current AI threat narrative About Signal // Noise Signal // Noise takes a real cybersecurity issue and runs it through multiple AI systems. We compare the findings, identify areas of agreement and disagreement, verify the evidence, and separate what matters from what does not. #Cybersecurity #ArtificialIntelligence #AI #CyberThreats #InfoSec #IncidentResponse #ThreatIntelligence #AgenticAI #Cybercrime #MSP

  ListenShow Notes
• 

  Episode #33

  Signal//Noise #033 - Hey! I'm Driving Here!

  Sep 6, 202626 minS1

  SIGNAL // NOISE | SN097 Episode: Hey! I'm Driving Here! Date: September 4, 2026 153M driver's license scans hit the dark web, including infrared and UV images banks trust. Here is who is exposed and what to do now. EPISODE OVERVIEW (description body, exactly 100 words) A dark web service called Nexus advertised searchable access to more than 153 million United States and Canadian driver's license scans. Each record held six images: front and back under visible light, infrared, and ultraviolet. Those non visible captures are what document authentication hardware reads to confirm a credential is genuine. Evidence points to identity verification provider IDScan.net , though nothing is confirmed. Chris Loehr and Bob Miller trace the attribution chain, the detection failure, and what relying parties should change. As always, they run the same incident through five AI engines and compare results live, including one that missed everything. WHAT WE COVER - How a journalist identified the likely source using nothing but GMT timestamps embedded in image filenames - Why infrared and ultraviolet license captures are a forgery input, not just a privacy loss - The Hertz and Planet13 correlation, and the negative evidence that ruled out airport and TSA systems - IDScan.net VeriScan retention defaults, and what Collect All plus Do not delete actually means in production - Why a year of continuous exfiltration produced no alert, and what egress detection should look for instead - MITRE ATT&CK coverage gaps when the incident is data brokerage rather than intrusion - How five AI engines handled the same source material, including one verifiability failure and two fabricated technique names KEY TAKEAWAYS - Treat the 153 million figure as a criminal seller claim, not a count of affected people - Inventory every ID capture point in your business and name the vendor behind each one - Contractually require deletion of document images within hours of the verification decision - Remove the license image as a standalone authenticator for account recovery, MFA removal, and credit origination - Tune egress detection for sustained low volume bulk retrieval rather than volume spikes ABOUT THE SHOW Signal // Noise is a cybersecurity podcast where Chris Loehr and Bob Miller break down the latest security incidents, threats, and trends. Each episode runs the same incident through five leading AI analysis tools (Claude, ChatGPT, Perplexity, Grok, and Gemini) then compares results live on air. Subscribe for weekly analysis that helps security professionals and business leaders stay ahead of emerging threats.

  ListenShow Notes
• 

  Episode #32

  Signal//Noise #032 - You Talking to Me?

  Sep 6, 202636 minS1

  SIGNAL // NOISE | SN032 | You talkin to me? Point72, Citadel, Millennium and Two Sigma were all hit by AI voice phishing. No malware, no exploit. Here is how it worked. EPISODE OVERVIEW A coordinated voice phishing campaign targeted four of the largest hedge funds in the United States and an undisclosed number of private equity firms, using cloned voices to talk employees into surrendering credentials and access. Two Sigma blocked its attempt. Point72 notified investors and is still reviewing. Citadel and Millennium declined to comment. Chris Loehr and Bob Miller break down what happened, why the technical perimeter at these firms was never even engaged, and what defenders should change this week. As always on Signal // Noise, the same incident is run through five AI analysis tools, Claude, ChatGPT, Perplexity, Grok, and Gemini, and the results are compared live on air. WHAT WE COVER - The full target list and what each firm has and has not confirmed - Why this attack involved no CVE, no malware, and no perimeter breach - The IT helpdesk impersonation playbook, step by step, from priming email to exfiltration - How commercial remote access tools become the implant with nothing malicious crossing the perimeter - The MITRE ATT&CK mapping, including T1566.004, T1656, and T1588.007 for adversary acquisition of AI tooling - Why there are zero published indicators of compromise, and what to hunt instead - The FBI FLASH alert from May documenting operatives showing up in person with USB drives - Where the five AI tools agreed, and where three of them fabricated specifics KEY TAKEAWAYS - Voice is no longer an identity factor, and detection training is the wrong defense - A written callback rule to a published internal number breaks this attack chain at step one - Helpdesk MFA resets performed on voice authority alone are the single highest risk control gap - Blocking the phone call does not close the incident, because the next attempt comes through a different channel - Confident formatting from an AI tool is not the same as a verified finding, and this episode shows exactly where that breaks ABOUT THE SHOW Signal // Noise is a cybersecurity podcast where Chris Loehr and Bob Miller break down the latest security incidents, threats, and trends. Each episode runs the same incident through five leading AI analysis tools (Claude, ChatGPT, Perplexity, Grok, and Gemini) then compares results live on air. Subscribe for weekly analysis that helps security professionals and business leaders stay ahead of emerging threats.

  ListenShow Notes
• 

  Episode #31

  Signal//Noise #031 - Return of the Worm

  Sep 6, 202630 minS1

  SIGNAL // NOISE SN031 Return of the Worm EPISODE OVERVIEW On August 4, 2026, an attacker took over the GitHub account behind keyv and cacheable, then published a self-replicating credential stealer to npm through the project's own release pipeline. Because the build was genuine, every poisoned package arrived carrying valid GitHub Actions provenance, and every provenance check passed. Chris Loehr and Bob Miller walk through the full attack chain, the persistence mechanism that hides in AI coding agent config files, and the response sequencing that most teams will get backwards. As always on Signal // Noise, the incident was run through five AI analysis tools (Claude, ChatGPT, Perplexity, Grok, and Gemini) and the results compared live on air, including one finding that only a single tool caught and one that another tool appears to have invented. WHAT WE COVER - How a maintainer account takeover produced npm packages with valid, verifiable build provenance - Why the npm preinstall lifecycle hook runs before your application code ever loads - The Bun runtime staging trick that sidesteps Node-focused monitoring - What the payload harvests: npm and GitHub tokens, AWS Secrets Manager, Kubernetes secrets, HashiCorp Vault, Stripe and Slack keys, SSH and TLS private keys - EtherHiding: rotating command-and-control infrastructure with a single Ethereum transaction - Persistence in .claude/settings.json and .vscode/tasks.json that survives full package remediation - The revocation watcher that makes credential rotation dangerous if you do it first - Where the five AI tools agreed, where one caught something the others missed, and where one made things up KEY TAKEAWAYS - Provenance proves origin, not intent, and the worm could generate its own valid attestations - npm 12 and later disables unapproved lifecycle scripts by default, which closed the primary path for teams already upgraded - Isolate the host and remove persistence before rotating any credential - Editor and AI agent configuration files are executable code that no dependency scanner reads - Version-level data beats package-name lists, because the same package has both clean and poisoned versions ABOUT THE SHOW Signal // Noise is a cybersecurity podcast where Chris Loehr and Bob Miller break down the latest security incidents, threats, and trends. Each episode runs the same incident through five leading AI analysis tools (Claude, ChatGPT, Perplexity, Grok, and Gemini) then compares results live on air. Subscribe for weekly analysis that helps security professionals and business leaders stay ahead of emerging threats.

  ListenShow Notes

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.