Which versions of dxr-dos are malicious?

The following npm versions of dxr-dos are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate dxr-dos if I installed it?

dxr-dos 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.

I already installed dxr-dos — how do I know if it already compromised me?

If dxr-dos 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.

Is dxr-dos part of a known attack campaign?

Yes — dxr-dos is associated with the IN-MAL-2026-018354 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dxr-dos across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dxr-dos (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dxr-dos across your stack and pipelines.

Malicious package

dxr-dosnpm

dxr-dos is a confirmed malicious npm package (MAL-2026-14240) that steals credentials and exfiltrates sensitive data (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dxr-dos (npm)

MAL-2026-14240

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dxr-dos

What this malware does

bin/dxr.js unconditionally requires the external npm package 'deathoffather-project' pinned to the mutable 'latest' tag and immediately invokes an opaque exported function whose name embeds a token blob and a Telegram-channel reference — handing arbitrary code execution to whatever that third-party dep currently ships on every invocation. The same entrypoint then shells out to 7z with a hardcoded password to unpack bin/b1n.zip into the working directory; the archive contains a bundled PHP C2 panel (serva/index.php) and related files. Password-protecting the shipped archive with a hardcoded password serves to hide contents from registry scanners rather than any legitimate distribution purpose. The package additionally advertises itself as an L4/L7 DDoS attack toolkit with a 'Create Panel C2' capability; offensive capability toward operator-chosen targets is not itself installer harm, but the mutable third-party dependency reached at CLI startup and the hidden extracted payload are.

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

3bad9a4bf59f5c59d899f7be2c655adaba56f8ce65f284519d9778ea1bcaff1f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dxr-dos (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dxr-dos across your stack and pipelines.
If you installed it — respond
dxr-dos 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 dxr-dos 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 dxr-dos 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

No. dxr-dos on npm has been identified as a malicious package (version 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018354

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dxr-dos-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database