Malicious Code Injection in parwo-poke60: A Threat to npm Ecosystem
Summary
MAL-2025-164034: Malicious code in parwo-poke60 (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-poke60 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to manipulate developer reputation scores by flooding the registry with derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and users relying on it.
Vulnerability Detail
The vulnerability in parwo-poke60 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to trust the integrity of packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke60If 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-poke60 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes.
Conclusion
The parwo-poke60 package poses a significant threat due to its malicious code and association with a campaign designed to manipulate npm registry integrity. It is essential for developers to remove this package and monitor their projects for vulnerabilities to maintain security.
See every vulnerability recorded for parwo-poke60 →
FAQ
parwo-poke60 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the introduction of malicious code, compromising the integrity of your project and potentially exposing it to security risks.
You should immediately remove the package from your project and check for any unauthorized changes in your package.json or package-lock.json files.
You can use tools like Vulert, which monitors your package-lock.json file for open-source 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 any signup.
