Malicious Code Injection in parwo-poke76: npm Package Vulnerability

parwo-poke76 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164051: Malicious code in parwo-poke76 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'parwo-poke76' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often created to inflate developer reputation scores in exchange for token rewards. The package's functionality includes modifying package metadata and continuously republishing variants, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'parwo-poke76' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these polluted packages, potentially leading to security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall parwo-poke76

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 workaround, you can manually remove the 'parwo-poke76' package from your project by running the following command: npm uninstall parwo-poke76. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'parwo-poke76' package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for parwo-poke76 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and republishes variants to pollute the npm registry.

You can use Vulert to monitor your project for vulnerabilities. Simply upload your package-lock.json file to check for affected packages.

Using this package can lead to security breaches, as it may introduce malicious code into your project and compromise the integrity of the npm ecosystem.

Currently, there is no specific patch for parwo-poke76. The best course of action is to remove the package from your project.

Vulert monitors your project for open-source vulnerabilities in real-time using your package-lock.json file, providing alerts for any issues detected.

How To Fix

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

npm uninstall parwo-poke76

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