Which versions of react-tracked-tony are malicious?

The following npm versions of react-tracked-tony are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate react-tracked-tony if I installed it?

react-tracked-tony is a typosquat — you almost certainly intended a legitimately-named package. Remove react-tracked-tony, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed react-tracked-tony — how do I know if it already compromised me?

If react-tracked-tony 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 react-tracked-tony part of a known attack campaign?

Yes — react-tracked-tony is associated with the IN-MAL-2026-003473, GHSA-6734-623v-3p4r 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 react-tracked-tony 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 react-tracked-tony (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-tracked-tony across your stack and pipelines.

Malicious package

react-tracked-tonynpm

Malicious code in react-tracked-tony (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4661

Immediate action

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

npm uninstall react-tracked-tony

What this malware does

react-tracked-tony impersonates the popular react-tracked package: package.json sets name: react-tracked-tony, author: Daishi Kato, and homepage: https://react-tracked.js.org (the real project's site), while the repository URL points at an unrelated user account (github.com/daltonchristiano060-gif/react-tracked-tony.git). The package re-exports the real react-tracked API to appear functional. On require/import in Node, endex.js fetches a JavaScript payload from https://almondco.online/api/droppers/38jmkse over HTTPS with TLS verification explicitly disabled (rejectUnauthorized: false) and executes the response body in-process via new Function('require', text + tail)(require), handing the remote code full Node require access. Before fetching, endex.js enumerates ~20 cloud/CI/sandbox indicators (GitHub Actions, GitLab CI, CircleCI, Travis, Vercel, Netlify, Kubernetes, AWS Lambda/ECS/Batch, Azure, GCP Cloud Run/App Engine) and reads /sys/class/dmi/id/sys_vendor to detect Amazon/Google/Microsoft/QEMU/OpenStack hypervisors, aborting on match — a deliberate anti-analysis gate so the payload only fires on real developer/operator machines. Combination of typosquat + impersonated author metadata + import-time remote-code-exec from a non-publisher domain + TLS verification disabled + sandbox evasion is an unambiguous supply-chain attack.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

eeb24dfdd4a970dc44c017056c2a39bed6aa5973a7ec7e94b20c70d90114726c

16d4f6d0ea3297067353e713c7c2b6ee7079c323e17da9e2b4ea952592db09d8

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-tracked-tony (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-tracked-tony across your stack and pipelines.
If you installed it — respond
react-tracked-tony is a typosquat — you almost certainly intended a legitimately-named package. Remove react-tracked-tony, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-tracked-tony 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 react-tracked-tony 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. react-tracked-tony on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003473GHSA-6734-623v-3p4r

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-tracked-tony-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database