Malicious Code Injection in joko-nasicampur79-ruro Package
Summary
MAL-2025-104625: Malicious code in joko-nasicampur79-ruro (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 joko-nasicampur79-ruro package is part of the npm ecosystem and appears to be associated with a token reward campaign for the tea.xyz protocol. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. However, it has been identified as malicious due to its harmful payload.
Vulnerability Detail
The vulnerability in the joko-nasicampur79-ruro package stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access and manipulation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-nasicampur79-ruro
If 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 measure, you can avoid using the joko-nasicampur79-ruro package and any other packages that exhibit similar behaviors. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The joko-nasicampur79-ruro package poses a significant security risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial to remove this package and monitor your dependencies to safeguard your projects from similar vulnerabilities.
See every vulnerability recorded for joko-nasicampur79-ruro →
FAQ
The vulnerability can lead to unauthorized modifications in your project, potential exposure of sensitive data, and pollution of the npm registry.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application using the Vulert playground at Vulert Scanner.
There is no patch available for this specific package. The recommended action is to uninstall it and remove any dependencies associated with it.
You should immediately uninstall the package and review your project for any other potentially malicious dependencies.
Yes, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the npm ecosystem.