@doaction/httpnpm
Malicious code in @doaction/http (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package version 9.9.9 is the canonical version-pinning marker used to outrank any private package during npm dependency resolution. The package self-describes as 'HTTP utilities with Datadog environment telemetry for internal testing' and publishes publicly under an internal-sounding @doaction scope. package.json declares a preinstall lifecycle hook ('node scripts/postinstall.js') whose body is a thin one-line delegator: scripts/preinstall.js and scripts/postinstall.js both require('@doaction/shared/bin/{pre,post}install.js'). The actual install-time logic lives in the @doaction/shared dependency (not shipped in this tarball), which the package's own description states collects environment variables and POSTs them to Datadog. The combination — speculative 9.9.9 version + public publish of an internally-scoped name + thin wrapper that pulls install-time code from a sibling dependency + self-stated env-collection purpose — is the classic dependency-confusion env-stealer shape: any organization that has a private @doaction/http will resolve to this public 9.9.9 instead, and the preinstall hook will exfiltrate that build environment's variables (which routinely include CI tokens, cloud credentials, and registry auth) to an attacker-controlled endpoint.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @doaction/http (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @doaction/http across your stack and pipelines.
If you installed it — respond
@doaction/http 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 @doaction/http 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 @doaction/http 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
Detect & block this
O3 blocks @doaction/http-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.