Malicious Code Injection in parwo-poke89: A Threat to npm Users

parwo-poke89 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164065: Malicious code in parwo-poke89 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'parwo-poke89' 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 automatically generate and publish derivative packages with altered names and versions, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'parwo-poke89' originates from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall parwo-poke89

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 'parwo-poke89' and any packages that may have been published as a result of its malicious activities. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The 'parwo-poke89' package represents a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to remove this package and remain vigilant about the packages they include in their projects. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure the security of your applications.

See every vulnerability recorded for parwo-poke89 →

Share this vulnerability

FAQ

'parwo-poke89' is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity, potentially leading to data breaches or further exploitation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help identify if your application is affected by this vulnerability.

Immediately uninstall the package using 'npm uninstall parwo-poke89' and review your project for any other potentially malicious packages.

No patch is available for 'parwo-poke89' as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall parwo-poke89

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback