Which versions of angular-trackjs are malicious?

The following npm versions of angular-trackjs are flagged malicious: 0.1.1, 0.2.0, 0.2.1, 0.2.99. Treat any of these as compromised.

How do I remediate angular-trackjs if I installed it?

Remove angular-trackjs from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed angular-trackjs — how do I know if it already compromised me?

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

Yes — angular-trackjs is associated with the GHSA-wm69-3896-655x, RLMA-2025-06061 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 angular-trackjs 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 angular-trackjs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging angular-trackjs across your stack and pipelines.

Malicious package

angular-trackjsnpm

Malicious code in angular-trackjs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191952

Immediate action

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

npm uninstall angular-trackjs

What this malware does

The package angular-trackjs 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

4 flagged

0.1.10.2.00.2.10.2.99

Indicators of compromise (SHA-256)

3dde8ff08d0afb7a55d925331147c0b3f0dfac896838dcb69f61986b164e1753

b4da35ac01bfc9a066ed18d5c2e49c7691f1e8378db128dfe45dd6ab15d49e57

a705f8c4ba90ae82431f8007849321606cce42b1ef10436896db41b730e088ed

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for angular-trackjs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging angular-trackjs across your stack and pipelines.
If you installed it — respond
Remove angular-trackjs from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If angular-trackjs 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 angular-trackjs 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. angular-trackjs on npm has been identified as a malicious package (versions 0.1.1, 0.2.0, 0.2.1, 0.2.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wm69-3896-655xRLMA-2025-06061

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks angular-trackjs-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