Malicious Code Injection in parwo-poke75: A Threat to npm Users
Summary
MAL-2025-164050: Malicious code in parwo-poke75 (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
parwo-poke75 is an npm package that is part of a broader campaign targeting developers through the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, which can mislead developers and inflate reputation scores. Its functionality is compromised by malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in parwo-poke75 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to potential misuse of developer credentials and reputation. This can result in a polluted npm registry, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke75If 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 parwo-poke75 package from your project by executing: npm uninstall parwo-poke75. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The parwo-poke75 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 take immediate action by uninstalling the package and monitoring their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for parwo-poke75 →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately and check for any updates or alternatives that do not contain this vulnerability.
Yes, the impacts include potential misuse of developer credentials, reputation inflation, and a polluted npm registry, making it harder to find legitimate packages.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security patches for your packages.
