Polymorphic malware is the kind of threat that changes its own code — its signature, its behavior, even the command-and-control server it reports to — specifically so your antivirus can't catch it. In this episode, Dr. Mike Saylor of Black Swan Cybersecurity joins Prasanna and me to break down exactly how this works, why signature-based detection keeps losing the race, and what defenders actually need to do differently.

Mike walks us through ViraLock, one of the most well-known early examples of polymorphic malware, and explains the gap between infection and detection that attackers exploit. We also get into the difference between polymorphic and metamorphic malware — and metamorphic is a lot scarier. Then we cover waterhole attacks, a red team story that will make you rethink how fast attackers can own a network, and what behavioral detection looks like when it's actually working.

If you thought keeping your antivirus updated was enough, this episode is going to change your mind.

Chapters:

00:00:00 – Intro

01:35 – Meet the guests: Prasanna Malaiyandi and Dr. Mike Saylor

02:58 – What is polymorphic malware? The ViraLock story

05:52 – How polymorphic code changes its own signature

10:04 – Disguised executables and the human factor

12:23 – Polymorphic vs. static malware: what's the real difference?

14:15 – Metamorphic malware: nation-state-level scary

16:01 – The Frankenstein virus: a conceptual metamorphic example

16:52 – Waterhole attacks: infecting the shared file everyone downloads

18:32 – How polymorphic malware stays alive: the red team story

21:28 – Behavioral detection and baselining: how you actually fight back

26:57 – Risk-based defense: protect what matters most

A PyPI software supply chain attack hit LiteLLM — a library pulled into developer environments 97 million times a month — and if you use it, you may already be compromised. This wasn't a fake package or a typo-squatting trick. Attackers stole real credentials, published malicious code as the real thing, and walked out with SSH keys, cloud credentials, Kubernetes tokens, API keys, and more — all encrypted and sent home before anyone knew what happened.

I'm doing something I've never done before: an emergency episode, recorded and published immediately because this is that serious. I brought in Dr. Mike Saylor, co-author of our book Learning Ransomware Response and Recovery, and my co-host Prasanna Malaiyandi to break down exactly what happened, how to find out if you were hit, and what you need to do to protect yourself going forward.

We open with a story from 1982 that perfectly captures what this attack really is — getting poisoned by something you trusted completely. That framing matters. This wasn't a failure of the library. It was a failure of the supply chain. And it can happen again.

Chapters:

00:00:00 - Intro: Why this is an emergency episode

00:01:35 - Meet the guests: Dr. Mike Saylor and Prasanna Malaiyandi

00:02:31 - The Tylenol poisoning analogy and what it means for software supply chains

00:05:51 - What LiteLLM is and what the malware actually did to your environment

00:09:04 - Dependencies explained: why you're affected even if you didn't install LiteLLM directly

00:12:24 - How to find out if you were hit: the first things to check right now

00:14:23 - IOCs and TTPs: what to look for in your logs and on your systems

00:19:07 - Network indicators: unusual traffic and what it tells you

00:22:12 - How security teams can find out if developers installed it without telling anyone

00:30:38 - Action items for the future: inventory, pinning, and hash verification

00:36:55 - Sandboxing new downloads before they touch your environment

00:37:59 - Immutable backups: why this attack makes the case for them

00:40:33 - Modern authentication: MFA, its limits, and why passkeys matter

00:46:53 - Where to get threat intel so you hear about attacks like this faster

00:53:23 - Wrap-up

If you installed or upgraded LiteLLM on or after March 24, 2026 without a pinned version, stop what you're doing and listen to this episode first.

The story:

https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack/

https://securitylabs.datadoghq.com/articles/litellm-compromised-pypi-teampcp-supply-chain-campaign/

https://snyk.io/articles/poisoned-security-scanner-backdooring-litellm/

https://www.wiz.io/blog/threes-a-crowd-teampcp-trojanizes-litellm-in-continuation-of-campaign

https://checkmarx.com/zero-post/python-pypi-supply-chain-attack-colorama/

https://www.upwind.io/feed/litellm-pypi-supply-chain-attack-malicious-release

https://docs.litellm.ai/blog/security-update-march-2026

https://www.helpnetsecurity.com/2026/03/25/teampcp-supply-chain-attacks/

https://www.darktrace.com/resources/the-cisos-guide-to-cyber-ai

https://securitylabs.datadoghq.com/articles/litellm-compromised-pypi-teampcp-supply-chain-campaign/

Resources:

https://www.stopransomware.com

https://www.cisa.gov

https://www.cve.org/

Fileless malware is one of the most dangerous attack types out there — it never writes to your hard drive, lives entirely in RAM, and can steal your credentials before your antivirus has any idea it's there. In this episode, I bring in Dr. Mike Saylor — my co-author on Learning Ransomware Response & Recovery — to break down exactly how this attack works, why it's so hard to detect, and what you can actually do to protect yourself.

Mike walks us through how fileless malware hides in memory, how bad guys maintain their foothold even after a reboot by modifying registry keys or rewriting the operating system itself, and why the ArcGIS attack is a perfect real-world example — attackers sitting undetected inside a network for two years. We also get into MFA, specifically why a lot of MFA setups are done wrong, why passkeys are the better answer, and when it's time to bring in an EDR or XDR tool.

Fair warning: the action items here are a bit more advanced than our usual stuff. Think of this as the 401k conversation — don't have it before you've built your emergency fund. But this is stuff you absolutely need to know.

00:01:26 - Welcome & intro

00:04:43 - What is fileless malware?

00:09:16 - How fileless malware achieves persistence (ArcGIS case study)

00:15:02 - Can fileless malware spread beyond one machine?

00:16:43 - Defending yourself: MFA done right

00:20:38 - Why passkeys beat MFA

00:23:00 - EDR and XDR explained

00:28:03 - How modern EDR tools detect fileless malware

00:30:01 - Wrap-up and action items