"Miasma" npm Worm Compromises 31 Red Hat Cloud Services Packages via CI/CD Hijack
"Miasma" npm Worm Compromises 31 Red Hat Cloud Services Packages via CI/CD Hijack is a critical-severity supply chain compromise issue in @redhat-cloud-services, a package. Affected: 31 @redhat-cloud-services npm packages (compromised June 1, 2026). It has been exploited in the wild.
Is @redhat-cloud-services running on your developers' machines? Anomity inventories the AI agents, MCP servers, extensions and skills on every developer device, so you can see what this advisory touches. Detect this across your developers' devices with Anomity →
Key facts
- ID
miasma-npm-worm-compromises-31-red-hat-cloud-services-packages-via-ci- Severity
- critical
- Attack type
- Supply chain compromise, Credential theft, Malware
- Component
- @redhat-cloud-services · package
- Package
@redhat-cloud-servicesnpm- Known exploited
- Yes
- Published
- Last verified
What is this vulnerability?
A self-propagating Mini Shai-Hulud variant dubbed "Miasma: The Spreading Blight" compromised 31 @redhat-cloud-services npm packages, not via typosquatting but by hijacking the publish pipeline through GitHub Actions OIDC tokens. A preinstall lifecycle hook drops a 4.2 MB obfuscated payload that harvests cloud keys, CI tokens, Vault and Kubernetes credentials, and SSH keys, and actively queries AWS Secrets Manager, Azure Key Vault, and GCP Secret Manager. It injects hooks into Claude, Copilot, and Gemini tooling and disguises exfiltration as traffic to a non-existent api.anthropic.com/v1/api route.
Affected versions
| Affected | Fixed in |
|---|---|
31 @redhat-cloud-services npm packages (compromised June 1, 2026) | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run 31 @redhat-cloud-services npm packages (compromised June 1, 2026).
How do I fix it?
Uninstall affected packages and reinstall from clean sources. Use npm ci --ignore-scripts in CI. Remove persistence files (kitty-monitor, gh-token-monitor) BEFORE revoking tokens to avoid the dead-man switch. Rotate all cloud, CI, and Git credentials. Rebuild runners from clean images.