Trapdex Subscribe

CampaignsPublisher / pipeline compromise

node-ipc dormant maintainer account taken over through an expired email domain

Am I affected?

  • node-ipc 9.1.6, 9.2.3 or 12.0.1 is in the dependency treeRead-only checkfind . -path "*node_modules/node-ipc/package.json" -exec grep -H version {} +
  • Lockfiles, build caches or the npm cache hold node-ipc.cjs with SHA-256 96097e0612d9575cb133021017fb1a5c68a03b60f9f3d24ebdc0e628d9034144

Do this now

  1. Pin node-ipc to a known-good version; rotate exposed secrets
  2. Require 2FA on dormant maintainer accounts; watch email domain expiry
  3. Alert on high-volume DNS TXT queries from build hosts

What happened

In May 2026, an attacker took over node-ipc via a lapsed maintainer email domain and published three stealer versions.

Affects: Node.js developers and CI runners that installed node-ipc 9.1.6, 9.2.3 or 12.0.1

  • npm

Attack chain

  1. Lure

    None; account recovery abuse through a re-registered maintainer email domain

    First seen

  2. Artifact

    node-ipc@9.1.6, 9.2.3 and 12.0.1 (node-ipc.cjs)

  3. Actor

    No source we cite attributes this activity to an actor.

  4. Infrastructure

    • HTTPS exfil domain
    • DNS TXT exfil zone

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
packagenode-ipc@12.0.1
packagenode-ipc@9.2.3
packagenode-ipc@9.1.6
domainsh[.]azurestaticprovider[.]net
ip37[.]16[.]75[.]69
sha25696097e0612d9575cb133021017fb1a5c68a03b60f9f3d24ebdc0e628d9034144

Defender actions

  1. Pin node-ipc to a known-good version and rotate secrets on hosts that loaded the bad versions
  2. Check maintainer email domains for expiry and require 2FA on dormant accounts
  3. Alert on high-volume DNS TXT queries from build hosts

Summary

A dormant maintainer's email domain lapsed and was re-registered on 7 May 2026, which let the new owner reset the npm password and gain publish rights. Three node-ipc versions then shipped an obfuscated stealer in the CommonJS entry point that exfiltrates developer and cloud credentials over HTTPS and DNS TXT queries.

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • The first-seen date is the domain re-registration date.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.