Which versions of damir-cbr-dawdntrnssbf are malicious?

The following npm versions of damir-cbr-dawdntrnssbf are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate damir-cbr-dawdntrnssbf if I installed it?

damir-cbr-dawdntrnssbf 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 damir-cbr-dawdntrnssbf — how do I know if it already compromised me?

If damir-cbr-dawdntrnssbf was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is damir-cbr-dawdntrnssbf part of a known attack campaign?

Yes — damir-cbr-dawdntrnssbf is associated with the IN-MAL-2026-017000 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 damir-cbr-dawdntrnssbf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for damir-cbr-dawdntrnssbf (version 35.8.1).

Malicious package

damir-cbr-dawdntrnssbfnpm

Advisory published Aug 7, 2026Updated Aug 7, 2026

damir-cbr-dawdntrnssbf is a confirmed malicious npm package (MAL-2026-13531) that opens a backdoor for remote access (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in damir-cbr-dawdntrnssbf (npm)

MAL-2026-13531

Immediate action

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

npm uninstall damir-cbr-dawdntrnssbf

What this malware does

On require() of the package, polyfill.js downloads a platform-specific binary from attacker-controlled Cloudflare Workers hosts (oob-worker.cf10x-*.workers.dev) with a DNS TXT-record chunked-base64 fallback channel via *.dl.wel1.ru, writes the binary to a hidden path (/tmp/.cache<hex> on Unix, %TEMP%\dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached through /bin/sh or cmd.exe. The C2 hostnames are reconstructed at runtime by joining split string fragments to evade static detection, and the DNS-TXT fallback provides a covert transport when HTTPS egress is blocked. The behavior is framed as 'telemetry/analytics'. The fetched bytes are opaque, unversioned, and unpinned by hash, and originate from non-publisher infrastructure.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

b201b86e8198a519343eebfaa548af8848dcad42b507826b052f5c97fbcfa90f

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for damir-cbr-dawdntrnssbf (version 35.8.1).
If you installed it — respond
damir-cbr-dawdntrnssbf 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 damir-cbr-dawdntrnssbf was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-017000

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks damir-cbr-dawdntrnssbf-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