Malicious Code Injection in parwo-poke72: A Threat to npm Packages
Summary
MAL-2025-164047: Malicious code in parwo-poke72 (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-poke72 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is designed to manipulate package metadata and publish numerous derivative packages, which can lead to reputation inflation for malicious actors. The vulnerability stems from its integration into a broader scheme that exploits npm's publishing mechanisms.
Vulnerability Detail
The vulnerability in parwo-poke72 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke72If 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, avoid using the parwo-poke72 package and any other packages associated with the tea.xyz campaign. Regularly audit your npm packages using the command: npm audit to identify and address vulnerabilities.
Conclusion
The parwo-poke72 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for parwo-poke72 →
FAQ
parwo-poke72 is an npm package identified as part of a malicious campaign that manipulates package metadata and floods the npm registry with derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and integrity.
You should uninstall the package immediately using npm uninstall parwo-poke72 and audit your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
