Malicious Code Injection in nadia-kripik36-breki Package
Summary
MAL-2025-74514: Malicious code in nadia-kripik36-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The nadia-kripik36-breki package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, but they pose significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the nadia-kripik36-breki package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. This allows the package to continuously republish variants with random names, polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently expose their projects to further vulnerabilities or malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nadia-kripik36-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 nadia-kripik36-breki package and any other packages associated with the tea.xyz token reward campaign. It is advisable to audit your project's dependencies using tools like npm audit to identify and address any vulnerabilities.
Conclusion
The nadia-kripik36-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove such packages from their projects to maintain security. Utilizing tools like Vulert can help in monitoring and addressing vulnerabilities effectively.
See every vulnerability recorded for nadia-kripik36-breki →
FAQ
The nadia-kripik36-breki package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
If your project includes the nadia-kripik36-breki package, it may expose your application to security risks, including the potential for malicious code execution and pollution of the npm registry.
You should uninstall the nadia-kripik36-breki package immediately using the command npm uninstall nadia-kripik36-breki and audit your project dependencies for any other vulnerabilities.
Regularly audit your dependencies using tools like npm audit, and stay informed about known vulnerabilities in the packages you use. Consider using Vulert to monitor your project for open-source vulnerabilities.
Vulert is a monitoring tool that uses your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software. You can check if your application is affected by vulnerabilities using the Vulert playground without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
