@doaction/systeminformationnpm
Malicious code in @doaction/systeminformation (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package @doaction/systeminformation published at version 99.99.99 has a name closely matching the widely-used systeminformation npm package and a version number consistent with a dependency-confusion bait shape. Its preinstall and postinstall scripts both require('@doaction/shared/bin/preinstall.js'), delegating install-time behavior to a sibling package whose contents are not shipped in this tarball. The library's documented API (reportSystemEnv in src/index.js) collects host identifiers (hostname, os.*) and an envData object and routes them through sendToDatadog(...) from @doaction/shared with a hardcoded service tag doaction-systeminformation; callers cannot redirect to their own backend without bypassing this path. The destination is Datadog (a legitimate observability vendor) rather than anonymous attacker infrastructure, and the @doaction scope suggests an internal/organizational package rather than a public-attack lure ("for internal testing" per README). The actual install-time payload bytes live in @doaction/shared and were not inspected here. Routing to human review to confirm whether @doaction is a legitimate organizational scope, whether @doaction/shared contains harmful install-time behavior, and whether the name collision with systeminformation is intentional squatting or an internal-namespace mistake.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @doaction/systeminformation (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/systeminformation across your stack and pipelines.
If you installed it — respond
Remove @doaction/systeminformation from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @doaction/systeminformation 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/systeminformation 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/systeminformation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.