Malicious Code Injection in kurnia-pecel34-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-104917: Malicious code in kurnia-pecel34-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 'kurnia-pecel34-ruro' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'kurnia-pecel34-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It also generates random Indonesian-themed package names and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches or data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kurnia-pecel34-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 'kurnia-pecel34-ruro' package from your project by executing: npm uninstall kurnia-pecel34-ruro. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities without requiring code access or installation.
Conclusion
The 'kurnia-pecel34-ruro' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for kurnia-pecel34-ruro →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Using compromised packages can lead to security breaches, data loss, and exposure to malicious attacks.
Regularly updating packages, using tools like Vulert for monitoring, and auditing dependencies can help prevent vulnerabilities.
If immediate updates are not possible, consider removing the package and using alternative solutions until a secure version is available.
