Malicious Code Injection in parwo-poke35: A Threat to npm Users
Summary
MAL-2025-164006: Malicious code in parwo-poke35 (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
The package parwo-poke35 is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in parwo-poke35 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, thereby polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke35If 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-poke35 package and monitor your project for any dependencies that may indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The parwo-poke35 package poses a significant risk to npm users due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for parwo-poke35 →
FAQ
parwo-poke35 is a malicious npm package associated with the tea.xyz token reward campaign, designed to manipulate package metadata.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the package immediately using 'npm uninstall parwo-poke35' and check for any other affected dependencies.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
