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

ucok-poke29 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169648: Malicious code in ucok-poke29 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ucok-poke29 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, thereby inflating developer reputation scores for token rewards. Its functionality is compromised by the presence of malicious scripts that alter package metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in ucok-poke29 originates from its association with the tea.xyz token reward campaign. The package contains scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This malicious behavior can lead to the proliferation of untrustworthy packages in the npm registry, potentially compromising the integrity of applications that depend on these packages. The continuous republishing of variants can also clutter the registry, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall ucok-poke29

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, you can avoid using ucok-poke29 and any other packages that are part of the malicious campaign. If you have already installed the package, ensure to remove it immediately and check your package-lock.json for any other affected packages.

Conclusion

The ucok-poke29 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take immediate action to remove affected packages. Regular monitoring and updating of dependencies are essential to maintain the security of applications.

See every vulnerability recorded for ucok-poke29 →

Share this vulnerability

FAQ

ucok-poke29 is an npm package identified as part of a malicious campaign that alters package metadata and publishes derivative packages to inflate developer reputation.

The vulnerability can lead to the inclusion of untrustworthy packages in your application, potentially compromising its security and integrity.

You should uninstall ucok-poke29 immediately using the command npm uninstall ucok-poke29 and check for any other affected packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall ucok-poke29

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