Malicious Code Detected in trevora-cir136: A Threat to npm Users
Summary
MAL-2025-169191: Malicious code in trevora-cir136 (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 package trevora-cir136 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, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in trevora-cir136 originates from its involvement in a token reward campaign that utilizes malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, thereby continuously republishing variants to the npm registry. This not only affects the reputation of developers but also poses a risk to users who may inadvertently install these compromised packages, leading to potential security breaches and instability in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir136If 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, you can avoid using trevora-cir136 and any other packages that may be part of the malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks. You can also use the following command to check for any outdated packages in your project: npm outdated.
Conclusion
The trevora-cir136 package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is crucial to uninstall this package and remain vigilant about the packages you use in your projects. Regular monitoring and updates can help safeguard your applications from such vulnerabilities.
See every vulnerability recorded for trevora-cir136 →
FAQ
trevora-cir136 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your application's integrity.
You should uninstall the package immediately using the command: npm uninstall trevora-cir136.
Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and avoid using packages from untrusted sources.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing package-lock.json. You can check if your application is affected by vulnerabilities using the Vulert playground without any signup.
