CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-16
HIGHupdatedNATOB1incident

node-ipc npm package backdoored, likely via an expired-domain account takeover: three malicious versions steal developer and CI credentials, flagged about three minutes after publication

node-ipc npm package backdoored, likely via an expired-domain maintainer takeover: three malicious versions steal developer and CI credentials on require()

Analysis

On 2026-05-14, three malicious versions of the node-ipc npm package (9.1.6, 9.2.3 and 12.0.1) were published at the same time by a co-maintainer account with no prior publish history on the package (StepSecurity, 2026-05-14). The account's email domain had expired on 2025-01-10 and was re-registered on 2026-05-07, a week before the attack (The Hacker News, 2026-05-14). Socket assesses that the new domain owner could then trigger a standard npm password reset and gain publish rights without touching the maintainer's own infrastructure (Socket Security, 2026-05-14). CSO counts almost 700K weekly downloads and 424 dependent projects, while StepSecurity reports over 10 million weekly downloads (CSO Online, 2026-05-15 · StepSecurity, 2026-05-14). The 9.x releases are fabricated from the 12.x package structure, so projects on ^9, ~9.1.x, ~9.2.x, ^12 or ~12.0 ranges received a malicious build on their next install or lockfile refresh (StepSecurity, 2026-05-14). When StepSecurity published, npm's latest tag pointed to 12.0.1, so an unpinned npm install node-ipc pulled the compromised tarball (StepSecurity, 2026-05-14). As of 2026-10-21 the npm registry no longer lists 9.1.6, 9.2.3 or 12.0.1, and its latest tag points to 14.0.0 (npm registry, 2026-10-21).

The payload is an 80 KB obfuscated function appended to the CommonJS bundle node-ipc.cjs. It runs on every require('node-ipc') and uses no npm lifecycle hook, so tools that only scan preinstall and postinstall scripts miss it (StepSecurity, 2026-05-14). ESM-only consumers do not load the malicious file unless another dependency or a direct require loads node-ipc.cjs (Socket Security, 2026-05-14). The payload forks a detached child Node process that collects cloud provider credentials, SSH keys, Kubernetes tokens, GitHub CLI configuration, Terraform state, CI workflow files, .env files, shell history and macOS Keychain databases, gzips them and exfiltrates them (Socket Security, 2026-05-14 · StepSecurity, 2026-05-14). Four stacked obfuscation layers (string-array shuffling, control-flow flattening, dead-code injection and a custom reversed-nibble base-16 encoding) resist static analysis (StepSecurity, 2026-05-14). Socket found no persistence and no second-stage download, and its scanner flagged the publish within roughly three minutes (Socket Security, 2026-05-14).

Contradiction: the analyses disagree on payload details. StepSecurity and The Hacker News describe 90+ file-path patterns, an HTTPS POST channel alongside DNS TXT exfiltration, and a SHA-256 targeting gate that leaves 12.0.1 inert except on one targeted project (StepSecurity, 2026-05-14 · The Hacker News, 2026-05-14). Socket counts 113 macOS and 127 Linux patterns, says the payload uses DNS TXT queries and not HTTP, HTTPS or TLS for exfiltration, and finds the same malicious file in all three versions, with a hash gate that only changes what the module exports (Socket Security, 2026-05-14). Treat all three versions as active stealers.

Updates3

Correction

As of 2026-09-30 no source said the malicious versions had been removed from the registry: when StepSecurity published, npm's latest tag pointed to the malicious 12.0.1 (StepSecurity, 2026-05-14). The payload fires on require() and uses no install hook, so disabling install scripts in CI does not stop it. Socket's advice is to review dependencies by their entrypoints and to rotate every secret on an affected host (Socket Security, 2026-05-14). Socket and StepSecurity disagree on the exfiltration channels, the pattern count and whether 12.0.1 is gated to one target (Socket Security, 2026-05-14 · StepSecurity, 2026-05-14), and all three versions should be treated as active. The entry previously named a domain registrar and Vue CLI and webpack tooling as dependents, which no cited source states.

Correction

Socket calls the expired recovery-email domain the likely vector and frames the mechanism conditionally, assuming the maintainer's npm recovery address was hosted on that domain (Socket Security, 2026-05-14); StepSecurity instead says the maintainer credentials were either freshly compromised or the account was added as a maintainer specifically for this publish (StepSecurity, 2026-05-14). How the account was taken over is therefore not established.

Improvement

As of 2026-10-21 the npm registry no longer lists 9.1.6, 9.2.3 or 12.0.1, and its latest tag points to 14.0.0 (npm registry, 2026-10-21), so a fresh unpinned install no longer resolves to a malicious version; the exposure now lies with hosts, build caches and local npm caches that already hold one of the three.

Sources5

Revision history

  1. Published 2026-05-16-5bc123a0
  2. Correction 2026-09-30T0639Z-audit

    Unsourced claims are removed: a named registrar, Vue CLI and webpack dependents, registry removal of the versions and an npm audit bypass, along with advice to run npm ci with scripts disabled, which does not stop a payload that fires on require(). The conflicting payload descriptions of Socket and StepSecurity are stated as a contradiction, so the title no longer asserts StepSecurity's pattern count. An attacker-controlled domain, the exfiltration DNS suffix, the maintainer email domain and account name and inline ATT&CK ids are removed, the truncated headline is rewritten, and the entry gains an ATT&CK mapping.

    Changed: body classification techniques headline summary title

  3. Correction 2026-10-11T1307Z-audit

    The expired-domain takeover is Socket's likely vector, not an established one, and StepSecurity offers a different explanation; the title, headline and summary now say likely. CSO Online's article is dated 2026-05-15, not 2026-05-14.

    Changed: title headline summary sources body

  4. Improvement 2026-10-21T0800Z-audit

    As of 2026-10-21 the npm registry no longer lists the malicious 9.1.6, 9.2.3 and 12.0.1 releases and its latest tag points to 14.0.0, so a fresh unpinned install no longer resolves to one of them; the exposure now lies with hosts and caches that already hold one of the three.

    Changed: sources body

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.