Malicious Code Injection in ucok-poke51: A Threat to npm Ecosystem
Summary
MAL-2025-169673: Malicious code in ucok-poke51 (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
ucok-poke51 is an npm package that is part of a broader campaign targeting developers through token rewards. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. This package, like others in the campaign, has been compromised to include malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in ucok-poke51 originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further vulnerabilities and security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ucok-poke51
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 avoid using ucok-poke51 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure no malicious packages are included. You can also use tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The ucok-poke51 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Regular audits of your dependencies can help maintain the security of your applications.
See every vulnerability recorded for ucok-poke51 →
FAQ
ucok-poke51 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The malicious code modifies package metadata, potentially leading to the use of compromised packages that can introduce security vulnerabilities into your application.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using npm uninstall ucok-poke51 and check for any dependencies that may rely on it.
Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.