Malicious Code Exploit in parwo-poke102: A Threat to npm Ecosystem
Summary
MAL-2025-163961: Malicious code in parwo-poke102 (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-poke102 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 inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem by introducing harmful scripts and altering package metadata.
Vulnerability Detail
The vulnerability in parwo-poke102 stems from its design to execute autopublish scripts that modify the package.json file. These modifications include removing private flags, changing version numbers, and generating random package names, which leads to the pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks to applications that may unknowingly depend on these compromised packages. The origin of this vulnerability is linked to the broader tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall parwo-poke102
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-poke102 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The parwo-poke102 package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the system for token rewards. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove affected packages is crucial for maintaining application security.
See every vulnerability recorded for parwo-poke102 →
FAQ
parwo-poke102 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command npm uninstall parwo-poke102 and audit your dependencies for any other malicious packages.
You can use tools like npm audit or Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.