Malicious Code Injection in jelek-rasisme-batu: A Threat to npm Packages
Summary
MAL-2025-157053: Malicious code in jelek-rasisme-batu (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 'jelek-rasisme-batu' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This package's functionality is compromised due to malicious code that alters its metadata and behavior.
Vulnerability Detail
The vulnerability in 'jelek-rasisme-batu' originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This leads to continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and project integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jelek-rasisme-batuIf 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 'jelek-rasisme-batu' package and monitor your project's dependencies for any malicious activity. Use the following command to audit your npm packages: npm audit.
Conclusion
The 'jelek-rasisme-batu' 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 remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for jelek-rasisme-batu →
FAQ
The primary risk is the modification of package metadata, which can lead to the proliferation of malicious packages in the npm registry, affecting project integrity.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should immediately remove the package from your project and check for any other affected dependencies.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.
The npm audit command scans your project for vulnerabilities in dependencies and provides recommendations for fixing them.
