Malicious Code Detected in citra-pecel12-pore: A Threat to npm Ecosystem
Summary
MAL-2025-97667: Malicious code in citra-pecel12-pore (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 'citra-pecel12-pore' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by generating numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'citra-pecel12-pore' originates from its inclusion in a malicious campaign that employs autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall citra-pecel12-poreIf 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, you can avoid using the 'citra-pecel12-pore' package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior.
Conclusion
The 'citra-pecel12-pore' package poses a significant threat due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for citra-pecel12-pore →
FAQ
The malicious code modifies package.json to remove private flags and generates numerous derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
It is advisable to remove the package immediately and check for any alternative packages that serve your needs without the associated risks.
Using this package can lead to security vulnerabilities, pollution of the npm registry, and potential issues with your project's integrity.
Regularly monitor your dependencies using tools like Vulert and stay updated on security advisories related to the packages you use.
