Malicious Code Injection in prayoga-poke12: A Threat to npm Ecosystem
Summary
MAL-2025-164508: Malicious code in prayoga-poke12 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The prayoga-poke12 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the creation of derivative packages. This vulnerability poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in prayoga-poke12 originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages include scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for users who unknowingly install these compromised packages. The malicious payload can compromise the integrity of applications relying on this package, leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prayoga-poke12If 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, avoid using the prayoga-poke12 package and any other packages that may be part of the malicious campaign. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The prayoga-poke12 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications against potential threats.
See every vulnerability recorded for prayoga-poke12 →
FAQ
prayoga-poke12 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks such as unauthorized access or data breaches.
You should uninstall the prayoga-poke12 package immediately and check your package-lock.json file for any references to it.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
