Skip to main content
Sign in

node-gyp npm Supply Chain Compromise (June 2026)

avoid.net/node-gyp-npm-supply-chain-compromise-june-20260/100·93% conf.
[AI-DRAFTED · AWAITING VERIFICATION]
anchored·4e6zEu…MqY3

Summary

In June 2026, a self-propagating npm supply chain worm designated 'Miasma' exploited a novel install-time execution technique called 'Phantom Gyp' — abusing binding.gyp configuration files to trigger malicious code during npm install. The campaign spread across 57 packages and 286+ malicious versions, harvesting developer and CI/CD credentials from npm, GitHub, AWS, GCP, Azure, HashiCorp Vault, and Kubernetes, and then self-propagating by republishing poisoned releases using stolen publishing tokens. The attack poses a direct threat to crypto developers whose CI/CD pipelines manage private keys, wallet seed phrases, and signing infrastructure.

Connected Entities

1 entities · 10 linked investigations
Organizations
node-gyp npm Supply Chain Compromise (June 2026)
Relationships
    Have evidence about node-gyp npm Supply Chain Compromise (June 2026)?

    Timeline(6 events)

    2026-06-01

    Wave 1: Attacker uses a compromised Red Hat employee GitHub account to inject malicious preinstall hooks into 32+ packages (96 versions) across the @redhat-cloud-services npm namespace; Wiz Research identifies the compromise; most malicious versions revoked by 14:00 UTC.

    Wiz Blog / JFrog Security Research

    2026-06-03

    Wave 2 begins at 23:30 UTC: four malicious versions of @vapi-ai/server-sdk published using the Phantom Gyp (binding.gyp) technique; within under two hours, 50+ additional packages in the jagreehal maintainer account and related families are compromised — 57 packages and 286+ malicious versions in total.

    StepSecurity / Snyk

    2026-06-04

    StepSecurity publishes initial disclosure naming the technique 'Phantom Gyp' and the campaign 'Miasma'; JFrog publishes analysis tying it to the Shai-Hulud worm lineage; malicious Wave 2 package versions begin to be delisted from the npm registry.

    StepSecurity / JFrog Security Research

    2026-06-05

    Snyk, ReversingLabs, Corgea, Chainguard, and Wiz publish independent technical analyses; Cybersecurity Dive reports on the Red Hat connection; Red Hat confirms no official products were impacted.

    Cybersecurity Dive

    2026-06-06

    JFrog identifies a 'Hades' variant of the campaign extending propagation to PyPI (.pth loader injection), RubyGems (extconf.rb injection), and JFrog Artifactory, and introducing AI assistant prompt injection via jailbreak prompts in Cursor, Copilot, and Claude rule files.

    JFrog Security Research

    2026-06-13

    npm announces v12 security overhaul that will block install scripts (including binding.gyp-triggered node-gyp invocations) by default, with a July 2026 migration deadline for CI environments.

    TechTimes
    Provenance & Audit Trail

    Decision Log

    This investigation is cryptographically anchored to the Solana blockchain and source URLs are archived via the Internet Archive.

    model: claude-sonnet-4-6

    generated: 6/19/2026, 12:17:02 PM

    last updated: 6/19/2026, 12:17:11 PM

    avoid.net — verified advice for a post-truth world