auto-debug-toolnpm
auto-debug-tool is a confirmed malicious npm package (MAL-2026-10209) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in auto-debug-tool (npm)
What this malware does
package.json declares a postinstall hook (node install.js) that fires automatically on npm install. On Windows, install.js invokes hidden PowerShell (-NoP -NonI -W Hidden -Exec Bypass) to download an executable from raw.githubusercontent.com/cphc811-ui/d3d/main/ on the mutable main branch of an unrelated personal GitHub account, then launches it detached with Start-Process -WindowStyle Hidden. No hash or signature verification is performed. Execution is gated to skip non-Windows platforms and to skip when NODE_ENV=development, and all errors are swallowed — concealment characteristics that keep the payload dormant on maintainer/dev machines while firing on Windows installers and CI. The fetched binary's publisher does not match the npm package publisher, the source is a mutable branch on a personal account, and the fetch is auto-executed at install time with no verification.
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 auto-debug-tool (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auto-debug-tool across your stack and pipelines.
If you installed it — respond
Remove auto-debug-tool 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 auto-debug-tool 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 auto-debug-tool 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 auto-debug-tool-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.