Malicious Code Injection in parwo-poke96: A Threat to npm Packages

parwo-poke96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164073: Malicious code in parwo-poke96 (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 Your last release was probably never penetration tested 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-poke96' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in 'parwo-poke96' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The malicious payload is part of a broader trend of using npm for nefarious purposes, impacting the trustworthiness of the ecosystem.

How To Fix

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

npm uninstall parwo-poke96

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 measure, you can avoid using 'parwo-poke96' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages and remove any that are suspicious or unnecessary.

Conclusion

The 'parwo-poke96' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential to remove this package and regularly audit your dependencies to maintain the security of your applications. Utilizing tools like Vulert can further enhance your ability to monitor for vulnerabilities.

See every vulnerability recorded for parwo-poke96 →

Share this vulnerability

FAQ

'parwo-poke96' is an npm package that has been identified as containing malicious code aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the installation of compromised packages, potentially introducing security risks and instability to your application.

You should uninstall 'parwo-poke96' immediately using the command 'npm uninstall parwo-poke96' and audit your other dependencies for similar vulnerabilities.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your npm packages, ensuring that you are aware of any potential threats.

How To Fix

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

npm uninstall parwo-poke96

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