Malicious Code Injection in prayoga-poke32: A Threat to npm Users
Summary
MAL-2025-164530: Malicious code in prayoga-poke32 (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
prayoga-poke32 is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous derivative packages with altered names and metadata. The vulnerability in prayoga-poke32 allows for the modification of critical package information, posing a significant risk to users relying on this package.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the prayoga-poke32 package, which includes scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The ramifications include unauthorized access to sensitive information and the risk of executing malicious code within applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prayoga-poke32If 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 avoid using the prayoga-poke32 package altogether. If it is already in use, consider replacing it with a trusted alternative package that provides similar functionality without the associated risks.
Conclusion
The prayoga-poke32 package poses a significant security risk due to its malicious code that alters package metadata. Users are advised to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your npm dependencies.
See every vulnerability recorded for prayoga-poke32 →
FAQ
prayoga-poke32 is an npm package involved in a token reward campaign that has been identified as malicious due to its scripts that manipulate package metadata.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially introducing malicious code and compromising security.
You should immediately uninstall the prayoga-poke32 package and check for any other affected packages in your project.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
