Malicious Code Vulnerability in prayoga-poke42: Exploitation of npm Packages

prayoga-poke42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164541: Malicious code in prayoga-poke42 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

prayoga-poke42 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm ecosystem. However, it has been identified as part of a malicious scheme that floods the npm registry with derivative packages, impacting the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in prayoga-poke42 originates from its association with a malicious campaign that employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This activity not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants leads to pollution of the npm registry, posing significant risks to developers relying on the integrity of npm packages.

How To Fix

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

npm uninstall prayoga-poke42

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 manually remove the prayoga-poke42 package from your project by running the following command: npm uninstall prayoga-poke42. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The prayoga-poke42 package is compromised by a malicious vulnerability that affects the npm ecosystem. It is essential to take immediate action to remove this package and monitor your projects for any potential impacts. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for prayoga-poke42 →

Share this vulnerability

FAQ

prayoga-poke42 is an npm package that has been associated with a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and compromising its security.

You should uninstall the prayoga-poke42 package immediately and monitor your project for any signs of compromise.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies, use tools to monitor for vulnerabilities, and stay informed about the packages you use in your projects.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall prayoga-poke42

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