Malicious Code Injection in xaver-kripik12-riris Package
Summary
MAL-2025-92366: Malicious code in xaver-kripik12-riris (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 xaver-kripik12-riris package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. The ramifications include potential exposure of sensitive data and the risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-kripik12-ririsIf 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 temporarily prevent the installation of this package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access.
Conclusion
The xaver-kripik12-riris package poses a significant security risk due to its malicious code injection. It is crucial to remove this package and monitor your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for xaver-kripik12-riris →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can lead to the exposure of sensitive data and may allow attackers to manipulate your project's dependencies.
You should remove the xaver-kripik12-riris package from your project and monitor for any updates or patches.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories for the packages you use.
