Miasma npm Worm: Supply Chain Attack via Phantom Gyp
Score: 9/10

Miasma npm Worm: Supply Chain Attack via Phantom Gyp

The Miasma threat actor is deploying a self-spreading npm worm that utilizes a 'Phantom Gyp' technique to execute code during installation, targeting cloud credentials and AI coding assistants.

Executive Summary

The Miasma threat actor has launched a sophisticated npm supply chain campaign, compromising at least 57 packages and over 286 malicious versions within a two-hour window. The campaign employs a novel execution method dubbed 'Phantom Gyp,' where code execution is triggered via a malicious `binding.gyp` file during `npm install`, bypassing security tools that only monitor `package.json` scripts. Major targets include the official Vapi.ai SDK and numerous packages by maintainer `jagreehal`.

The attack chain involves a four-stage obfuscated payload that downloads a standalone Bun runtime to execute a credential harvester outside of Node.js monitoring. Beyond stealing multi-cloud credentials (AWS, GCP, Azure) and GitHub tokens, the malware poisons AI coding assistant configurations (Claude, Cursor, Gemini) by injecting persistent backdoors into developer environments. The worm also attempts to forge Sigstore provenance to maintain legitimacy. This campaign represents a high-urgency threat due to its self-propagating nature and its focus on poisoning modern AI-driven development workflows.

Key Details

Threat Name

Miasma npm Worm

Affects

—

Adversary

Miasma

Malware/Tools

Miasma

Report Score

9out of 10
Quality Score
Excellent
IOC Quality9
TTP Details9
Detection Guidance7
Enterprise Relevance10
Clarity & Structure9
Technical Depth10

Sources