Critical Malicious Code Vulnerability in @trackstar/test-angular-package

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191325: Malicious code in @trackstar/test-angular-package (npm). Affects @trackstar/test-angular-package versions 0.0.9. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @trackstar/test-angular-package is an npm package designed for Angular applications, providing various testing utilities. However, it has been compromised, leading to severe security risks for any system utilizing it. The package's functionality is overshadowed by its vulnerability to malicious code, which can lead to unauthorized access and data breaches.

Vulnerability Detail

This vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the package. The malicious payload is designed to steal tokens and credentials, publishing them to GitHub. It can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying the user's home directory, making it a critical threat to system integrity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @trackstar/test-angular-package

If 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 temporary measure, avoid using the @trackstar/test-angular-package until it has been confirmed safe. Regularly monitor your systems for any unauthorized access or changes.

Conclusion

The @trackstar/test-angular-package has been compromised by a malicious worm, posing significant risks to any system that uses it. Immediate action is required to remove the package and secure any affected systems. Regular monitoring and updates are essential to prevent future vulnerabilities.

See every vulnerability recorded for @trackstar/test-angular-package →

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys stored on the affected system.

The malicious code can steal sensitive information, propagate to other packages, and potentially destroy your home directory.

Yes, you can use Vulert's playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

If not addressed, this vulnerability can lead to data breaches, loss of sensitive information, and compromise of other systems.

It is advisable to avoid using this package until it has been verified as safe and free from malicious code.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @trackstar/test-angular-package

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback