Which versions of tracker-cloudflare are malicious?

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

How do I remediate tracker-cloudflare if I installed it?

tracker-cloudflare 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 tracker-cloudflare — how do I know if it already compromised me?

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

Yes — tracker-cloudflare is associated with the IN-MAL-2026-020010 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 tracker-cloudflare across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tracker-cloudflare (version 1.0.0).

Malicious package

tracker-cloudflarenpm

Advisory published Sep 11, 2026Updated Sep 11, 2026

tracker-cloudflare is a confirmed malicious npm package (MAL-2026-16140) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tracker-cloudflare (npm)

MAL-2026-16140

Immediate action

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

npm uninstall tracker-cloudflare

What this malware does

The package's preinstall hook runs node index.js, which collects host identifiers (os.hostname, os.userInfo, homedir, DNS servers, cwd) along with the contents of /etc/passwd and /etc/hosts, and POSTs the payload over HTTPS to the Burp Collaborator subdomain c6j5cmm8sia88v4zyhykqvhvcmid65uu.oastify.com. The package has empty description/author metadata and no legitimate functionality beyond this beacon. The exfiltration fires automatically on npm install before any consumer code runs.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

55b5bacf5779f1a1fa161ee38acbf61fda0dc18b3d0fe35213e2b0dc230c06e4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tracker-cloudflare (version 1.0.0).
If you installed it — respond
tracker-cloudflare 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 tracker-cloudflare 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. tracker-cloudflare 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-020010

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tracker-cloudflare-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