Malicious Code Injection in joko-asinan61-ruro Package
Summary
MAL-2025-104572: Malicious code in joko-asinan61-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-asinan61-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the joko-asinan61-ruro package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can inflate developer reputation scores fraudulently, posing risks to developers and users relying on the npm registry for secure packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-asinan61-ruroIf 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 joko-asinan61-ruro package in your project. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The joko-asinan61-ruro package contains malicious code that poses significant risks to developers and users. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for joko-asinan61-ruro →
FAQ
The malicious code can lead to the unauthorized modification of your package.json file, potentially compromising your project's integrity and security.
You can check your package-lock.json file for the presence of joko-asinan61-ruro or use tools like Vulert to scan for vulnerabilities.
Immediately remove the joko-asinan61-ruro package from your project and check for any other affected dependencies.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using your package-lock.json file.
While the npm registry is generally reliable, it is crucial to regularly audit your dependencies and use tools to monitor for vulnerabilities.
