Malicious Code Injection in prayoga-poke2: npm Package Vulnerability
Summary
MAL-2025-164516: Malicious code in prayoga-poke2 (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-poke2 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 deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in prayoga-poke2 arises from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to autopublish scripts that automate the generation of derivative packages, posing significant risks such as code injection, dependency confusion, and potential exploitation of applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prayoga-poke2If 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 remove the prayoga-poke2 package from your project by executing the command: npm uninstall prayoga-poke2. This will prevent any malicious code from executing while you assess your project's dependencies.
Conclusion
The prayoga-poke2 package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package and monitoring your project for vulnerabilities using tools like Vulert.
See every vulnerability recorded for prayoga-poke2 →
FAQ
prayoga-poke2 is an npm package used in JavaScript development, but it has been compromised to include malicious code.
The vulnerability can lead to unauthorized code execution, dependency confusion, and potential exploitation of your application.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
