Malicious Code Injection in joko-mieayam60-ruro Package
Summary
MAL-2025-104619: Malicious code in joko-mieayam60-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
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 joko-mieayam60-ruro package is part of the npm ecosystem, often used in JavaScript applications. 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 publishing scripts, which can lead to significant security risks for users who inadvertently install them.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the joko-mieayam60-ruro package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The ramifications include unauthorized access to sensitive data, disruption of application functionality, and damage to developer reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-mieayam60-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, avoid using the joko-mieayam60-ruro package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert, which can monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The joko-mieayam60-ruro package poses a significant security threat due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain application integrity.
See every vulnerability recorded for joko-mieayam60-ruro →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using npm uninstall joko-mieayam60-ruro and check your project for any other affected packages.
Yes, Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time.
Using this package can lead to unauthorized access to sensitive data, application disruptions, and damage to your reputation as a developer.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
