Malicious Code Injection in parwo-poke28: A Threat to npm Ecosystem

parwo-poke28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163998: Malicious code in parwo-poke28 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

parwo-poke28 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate package metadata and inflate developer reputation scores through automated scripts. Its functionality is compromised, making it a vector for malicious activities within the npm ecosystem.

Vulnerability Detail

The vulnerability in parwo-poke28 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with derivative packages. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the pollution of the npm registry and poses risks to developers relying on these packages for legitimate purposes.

How To Fix

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

npm uninstall parwo-poke28

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-poke28 and any other packages that are part of the tea.xyz campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The parwo-poke28 package poses a significant risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package from their projects and regularly audit their dependencies to maintain a secure development environment.

See every vulnerability recorded for parwo-poke28 →

Share this vulnerability

FAQ

parwo-poke28 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated scripts.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust package sources and potentially introducing malicious code into your project.

You should uninstall the package immediately using 'npm uninstall parwo-poke28' and review your project for any other potentially malicious packages.

You can use tools like npm audit to regularly check for vulnerabilities in your project dependencies. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall parwo-poke28

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