Malicious Code Injection in parwo-poke32: A Threat to npm Ecosystem
Summary
MAL-2025-164003: Malicious code in parwo-poke32 (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-poke32 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to participate in the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores by publishing numerous derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in parwo-poke32 stems from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to reputation inflation and potential security risks for users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke32If 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, you can avoid using the parwo-poke32 package until a secure version is released. Additionally, consider using the following command to uninstall the package: npm uninstall parwo-poke32.
Conclusion
The parwo-poke32 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for parwo-poke32 →
FAQ
parwo-poke32 is an npm package involved in a malicious campaign that inflates developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
If you have installed parwo-poke32, it is advisable to uninstall it immediately and monitor for any updates or patches from the package maintainers.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
