Malicious Code Injection in ucok-poke56: A Threat to npm Ecosystem

ucok-poke56 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169678: Malicious code in ucok-poke56 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

ucok-poke56 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in ucok-poke56 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ucok-poke56

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 the ucok-poke56 package and replace it with a known, secure alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The ucok-poke56 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for ucok-poke56 →

Share this vulnerability

FAQ

ucok-poke56 is an npm package identified as part of a malicious campaign that manipulates the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and its dependencies.

You should uninstall the package immediately using npm uninstall ucok-poke56 and review your project's dependencies for any other malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor your project for vulnerabilities in real-time, ensuring that you are alerted to any potential threats.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ucok-poke56

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback