Critical Malicious Code Vulnerability in @trackstar/test-package
Summary
MAL-2025-191326: Malicious code in @trackstar/test-package (npm). Affects @trackstar/test-package versions 1.1.5. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @trackstar/test-package is an npm package designed for testing purposes within the JavaScript ecosystem. It is utilized by developers to facilitate various testing scenarios in their applications. However, this package has been compromised, making it a significant security risk for any system that has it installed.
Vulnerability Detail
The vulnerability stems from a malicious code injection within the @trackstar/test-package, attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials, publishing them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The potential ramifications include complete system compromise, loss of sensitive data, and destruction of the user's home directory.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @trackstar/test-packageIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users should consider isolating the affected environment and ensuring that no sensitive information is stored on the compromised system. It is also advisable to monitor for any unusual activity that may indicate further exploitation.
Conclusion
The @trackstar/test-package has been identified as a critical security risk due to the presence of malicious code. Immediate action is required to mitigate potential damage, including uninstalling the package and rotating sensitive credentials. Users are encouraged to monitor their systems closely and utilize tools like Vulert for ongoing vulnerability management.
See every vulnerability recorded for @trackstar/test-package →
FAQ
You should immediately uninstall the package and rotate any sensitive credentials stored on the affected system.
The vulnerability was introduced through a malicious npm worm that injected harmful code into the package.
No, the package is considered compromised and should not be used until a secure version is released.
Signs may include unusual network activity, unauthorized access to accounts, or unexpected changes to files and directories.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
