Skip to content

Miasma Campaign

Named by 6 kept items in this workspace.

Search every workspace for Miasma Campaign. It matches the name as written, so it can find other things that share it.

The items that name it 6

  • article2026-10-29It is written here as Miasma campaign (targeted Red Hat npm packages, reused and extended Shai-Hulud code).

    targeted Red Hat npm packages, reused and extended Shai-Hulud code

  • writeup2026-10-29It is written here as Miasma campaign (targeted Red Hat npm packages; reused and extended Shai-Hulud code).

    targeted Red Hat npm packages; reused and extended Shai-Hulud code

  • writeup2026-07-12

    Rolling npm supply-chain compromise campaign publishing 57 packages across 286+ malicious versions in under two hours on June 3, including @vapi-ai/server-sdk, ai-sdk-ollama, and the jagreehal package family; referenced as a separate campaign from the jscrambler compromise, blocked for StepSecurity

  • writeup2026-07-01

    Earlier campaign published June 3, 2026, that compromised 57 npm packages across 286+ versions using the same CI/CD attack toolkit (Phantom Gyp binding.gyp hook, three-layer obfuscation, Bun runtime evasion). Published in a rolling campaign lasting under two hours. Documented in a separate StepSecur

  • writeup2026-06-18

    Campaign name referenced in relation to compromised packages including @vapi-ai/server-sdk, ai-sdk-ollama, and the jagreehal package family, added to StepSecurity's compromised-package database within minutes of detection

  • talk2026-06-03

    npm worm campaign starting June 1st 2026, initially compromised 32 Red Hat @redhat-cloud-services packages, expanded to over 80 packages and 286+ malicious versions within days; first confirmed in-the-wild use of TeamPCP's open-sourced MiniShai Hulud worm; multi-ecosystem (npm, PyPI, RubyGems), with

All threat actors in this workspace.