Malicious Code Injection in nurul-klanting61-riris Package
Summary
MAL-2025-88898: Malicious code in nurul-klanting61-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 nurul-klanting61-riris package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are intended to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the nurul-klanting61-riris package stems from its malicious payload that modifies the package.json file. This payload removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-klanting61-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 temporary workaround, avoid using the nurul-klanting61-riris package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to ensure no malicious packages are present.
Conclusion
The nurul-klanting61-riris package contains a significant vulnerability that can compromise the integrity of your project and the npm registry. It is crucial to remove this package and monitor your dependencies for any potential risks. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source projects.
See every vulnerability recorded for nurul-klanting61-riris →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks if compromised packages are used.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
