Malicious Code Injection in ucok-poke26: A Threat to npm Users

ucok-poke26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169645: Malicious code in ucok-poke26 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

ucok-poke26 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 random names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in ucok-poke26 originates from its association with the tea.xyz token reward campaign. The package contains scripts (auto.js, autopublish.js, etc.) that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. Users may unknowingly install these malicious packages, leading to security risks and loss of trust in the npm platform.

How To Fix

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

npm uninstall ucok-poke26

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 measure, avoid using the ucok-poke26 package and monitor your dependencies for any similar malicious packages. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities. For example, you can check your application using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The ucok-poke26 package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your projects. Utilizing tools like Vulert can help keep your application secure.

See every vulnerability recorded for ucok-poke26 →

Share this vulnerability

FAQ

ucok-poke26 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious packages that compromise the integrity of your project and the npm ecosystem.

You should uninstall the ucok-poke26 package immediately using 'npm uninstall ucok-poke26' and check for any other affected packages.

You can use tools 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 any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ucok-poke26

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