Malicious Code Injection in rweekk Package: A Threat to npm Users
Summary
MAL-2025-98327: Malicious code in rweekk (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 rweekk package is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm registry with malicious packages. This package is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names, thus compromising the integrity of the npm ecosystem.
Vulnerability Detail
The rweekk package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, while simultaneously polluting the npm registry with numerous derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of multiple malicious npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rweekk
If 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 measure, consider using npm audit to identify and remove any affected packages. You can run the following command in your terminal: npm audit fix. This will help mitigate the risk while you assess your dependencies.
Conclusion
The rweekk package poses a significant threat to npm users due to its malicious code designed to manipulate package reputation and pollute the npm registry. Immediate action is required to remove this package and monitor for any further vulnerabilities in your dependencies.
See every vulnerability recorded for rweekk →
FAQ
The rweekk package is a malicious npm package associated with the tea.xyz token reward campaign, designed to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing further security risks.
You should remove the rweekk package from your project immediately and check for any other affected packages using npm audit.
Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.