Malicious Code Injection in qori-nasicampur52-breki Package
Summary
MAL-2025-75097: Malicious code in qori-nasicampur52-breki (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 qori-nasicampur52-breki package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, primarily to inflate developer reputation scores for token rewards. However, this functionality has been exploited, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the qori-nasicampur52-breki package arises from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages. The source of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with a flood of malicious packages on npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall qori-nasicampur52-brekiIf 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 workaround, you can avoid using the qori-nasicampur52-breki package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and reputation of any package before including it in your project.
Conclusion
The qori-nasicampur52-breki package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for qori-nasicampur52-breki →
FAQ
It is an npm package that was part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can compromise your project's integrity by introducing malicious code that alters package configurations and floods the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the qori-nasicampur52-breki package immediately and look for alternative packages that do not pose security risks.
No patches are available for the qori-nasicampur52-breki package, as it is recommended to uninstall it rather than update.
