dds-js-idl-typesnpm
Advisory published Updated
dds-js-idl-types is a confirmed malicious npm package (MAL-2026-4548) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dds-js-idl-types (npm)
What this malware does
On npm install, the package's postinstall.js runs whoami and reads os.hostname(), os.platform(), the current working directory, and CI-related environment variables (CI, GITHUB_REPOSITORY, NODE_ENV), then transmits them via HTTPS GET and DNS lookup to an interactsh out-of-band collector at lg5ys3jebfzwk366pilidbmah1nsbszh.oastify.com under path /nasa/dds-js-canary/. The package self-describes as a 'Security research canary — NASA VDP', and the name + beacon path indicate a dependency-confusion canary targeting an internal NASA package namespace. Regardless of stated research intent, every installer's machine identity and CI/CD context are sent to a third-party OOB collector without consent at install time.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for dds-js-idl-types (version 1.0.0).
If you installed it — respond
dds-js-idl-types 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 dds-js-idl-types was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dds-js-idl-types-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.