Malicious Code Injection in trevora-cir38: npm Package Vulnerability
Summary
MAL-2025-169232: Malicious code in trevora-cir38 (npm). Affected versions are not published. 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 trevora-cir38 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in trevora-cir38 stems from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. This not only compromises the security of the affected packages but also misleads developers and users relying on the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir38If 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, consider using a package-lock.json file to lock your dependencies to specific versions. This can help prevent the installation of compromised packages. Additionally, you can monitor your dependencies for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The trevora-cir38 package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for trevora-cir38 →
FAQ
trevora-cir38 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the installation of malicious code that modifies your project's dependencies and can compromise its security.
You should uninstall the package immediately using 'npm uninstall trevora-cir38' and monitor your project for any unusual behavior.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
