Malicious Code Injection in ucok-poke35: A Threat to npm Ecosystem
Summary
MAL-2025-169655: Malicious code in ucok-poke35 (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-poke35 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of ucok-poke35 lies in its ability to modify critical package files, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in ucok-poke35 stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of downstream applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ucok-poke35If 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-poke35 and any other packages that may be part of the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The ucok-poke35 package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and repopulates the registry with harmful variants. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.
See every vulnerability recorded for ucok-poke35 →
FAQ
ucok-poke35 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package generation.
The vulnerability can lead to the modification of your project's package.json file, potentially introducing security risks and cluttering the npm registry with malicious packages.
You should uninstall the package immediately using 'npm uninstall ucok-poke35' and check your project for any other affected packages.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
