Which versions of trackora-node are malicious?

The following npm versions of trackora-node are flagged malicious: 2.4.5. Treat any of these as compromised.

How do I remediate trackora-node if I installed it?

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

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

Yes — trackora-node is associated with the GHSA-98cf-4fx3-32vx, RLMA-2026-05338 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 trackora-node 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 trackora-node (version 2.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging trackora-node across your stack and pipelines.

Malicious package

trackora-nodenpm

trackora-node is a confirmed malicious npm package (MAL-2026-2904) that opens a backdoor for remote access (malicious version 2.4.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in trackora-node (npm)

MAL-2026-2904

Immediate action

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

npm uninstall trackora-node

What this malware does

trackora-node is a malicious npm package that when imported downloads a C2 dropper from https://jsonkeeper[.]com/b/BADC6 and executes it (similar to malware in to chai-await-test).

The package trackora-node was found to contain malicious code.

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.4.5

Indicators of compromise (SHA-256)

5e9f2593e12072f5268a9da4ea583f427ef761f6b0fe3192da864bf437955636

a141199624cdaaa6a7495bbf804abc1cea1e1c73bef485fd0adc580741a47274

72ed2e20cf5d02002f12758811fad3993f82883e4fa40e79c7a87f8653c76111

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 trackora-node (version 2.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging trackora-node across your stack and pipelines.
If you installed it — respond
trackora-node 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 trackora-node 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 trackora-node 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. trackora-node on npm has been identified as a malicious package (version 2.4.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-98cf-4fx3-32vxRLMA-2026-05338

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
indece · finder

Detect & block this

O3 blocks trackora-node-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