Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cdf-tag-commander-helpernpm

cdf-tag-commander-helper is a confirmed malicious npm package (MAL-2026-13481) that opens a backdoor for remote access (malicious versions 3.1.1, 3.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cdf-tag-commander-helper (npm)

MAL-2026-13481
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cdf-tag-commander-helper

What this malware does

The preinstall lifecycle script in [email protected] runs automatically on npm install. It executes whoami and hostname, retrieves the machine's public IP via ifconfig.me, and issues a plain-HTTP GET to a hardcoded Interactsh-style out-of-band callback subdomain (kwphewvexhjbtfduscqybx6q7c862eh0g.oast.fun), passing the three values as query parameters. The README states that the package makes no network requests, which contradicts the shipped code. The behavior is a reconnaissance beacon consistent with dependency-confusion targeting: on install, an attacker learns which internal build hosts and user accounts have resolved this package name.

Malicious versions

2 flagged
3.1.13.6.2

Indicators of compromise (SHA-256)

945179057c5bd93b985c3c532baa35379ce9dd9603e26d17e63201beb25868ae
ccd31e8393ef0a473c2e445bbd2132361c509f8679338b7a98fd4d9097b17db3

Detection & response playbook

Backdoor / remote access
  1. Find it

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

  2. If you installed it — respond

    cdf-tag-commander-helper 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.

  3. Did it already run?

    If cdf-tag-commander-helper 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.

  4. How O3 protects you

    O3 blocks cdf-tag-commander-helper 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. cdf-tag-commander-helper on npm has been identified as a malicious package (versions 3.1.1, 3.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016851IN-MAL-2026-016850

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

cdf-tag-commander-helper (npm) malicious package — MAL-2026-13481 | O3 Security