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

ucok-poke74 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169698: Malicious code in ucok-poke74 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package ucok-poke74 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of ucok-poke74 lies in its ability to modify package.json files, remove private flags, and republish variants, thus polluting the npm registry.

Vulnerability Detail

The vulnerability in ucok-poke74 originates from its design to execute autopublish scripts that manipulate package metadata. This includes altering version numbers and generating random package names, which can lead to the proliferation of malicious packages in the npm ecosystem. The ramifications include potential security risks for developers who unknowingly install these packages, as they may contain harmful code that compromises their applications.

How To Fix

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

npm uninstall ucok-poke74

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, avoid using the ucok-poke74 package and monitor your project's dependencies for any malicious packages. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities.

Conclusion

The ucok-poke74 package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive can help safeguard your applications from such threats.

See every vulnerability recorded for ucok-poke74 →

Share this vulnerability

FAQ

ucok-poke74 is an npm package identified as malicious, designed to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to the installation of malicious code, potentially compromising your application's security and integrity.

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

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall ucok-poke74

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