Malicious Code Injection in parwo-poke34: A Threat to npm Ecosystem
Summary
MAL-2025-164005: Malicious code in parwo-poke34 (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-poke34 is an npm package that has been implicated in a malicious campaign targeting the npm registry. This package is part of the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary functionality of parwo-poke34 is to serve as a placeholder or utility package, but its malicious nature undermines its intended use, making it a significant threat to developers and their projects.
Vulnerability Detail
The vulnerability in parwo-poke34 originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke34
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 workaround, you can avoid using the parwo-poke34 package altogether. If it is already included in your project, remove it by executing the following command: npm uninstall parwo-poke34. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The parwo-poke34 package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for parwo-poke34 →
FAQ
parwo-poke34 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the inclusion of compromised packages in your project, which may introduce security risks and affect the integrity of your application.
You should uninstall the package immediately using the command: npm uninstall parwo-poke34.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities in your application using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and avoid using unverified packages from the npm registry.