Malicious Code Injection in eka-klanting37-ruro: A Threat to npm Packages
Summary
MAL-2025-101909: Malicious code in eka-klanting37-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 package 'eka-klanting37-ruro' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores for token rewards. Its functionality includes creating random package names and modifying existing package metadata, which can lead to significant issues within the npm registry.
Vulnerability Detail
The vulnerability in 'eka-klanting37-ruro' stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. This code generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. The origin of this vulnerability is linked to a broader campaign aimed at exploiting the npm ecosystem for fraudulent token rewards, posing risks such as reputation damage for developers and potential security threats to users of the affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eka-klanting37-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 remove the 'eka-klanting37-ruro' package from your project by executing the command: 'npm uninstall eka-klanting37-ruro'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'eka-klanting37-ruro' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to update or remove this package to safeguard your application from potential threats. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.
See every vulnerability recorded for eka-klanting37-ruro →
FAQ
The primary risk is the injection of malicious code that alters package metadata and floods the npm registry with unwanted variants, which can damage developer reputations and compromise security.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using unverified packages from the npm registry.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
You can visit the Vulert website for detailed insights and monitoring tools for open-source vulnerabilities in your software.
