did-0091npm
Malicious code in did-0091 (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, the package's postinstall script runs node -e to fetch the installer's public IP from api.ipify.org, execute id || ver && whoami && hostname, and collect hostname, cwd, and USERDOMAIN/COMPANY environment variables. The bundle is POSTed to a hardcoded interactsh subdomain at lszakfghwnvxspyfcmaabd1css99rnq3w.oast.fun. The package has no legitimate function: description is 'xxx', main file index.js is 0 bytes, and the only behavior is the install-time beacon. Combined with the unusual name shape, this matches dependency-confusion reconnaissance campaigns that probe corporate networks via Project Discovery's interactsh out-of-band service.
The OpenSSF Package Analysis project identified 'did-0091' @ 11.0.6 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for did-0091 (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging did-0091 across your stack and pipelines.
If you installed it — respond
did-0091 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If did-0091 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks did-0091 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks did-0091-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.