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

ucok-poke9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169701: Malicious code in ucok-poke9 (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-poke9 is a package within the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the distribution of software packages, but it has been compromised to include malicious scripts that manipulate package metadata. This vulnerability poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in ucok-poke9 stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags and alters version numbers, generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting users.

How To Fix

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

npm uninstall ucok-poke9

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 ucok-poke9 and any packages that depend on it. Additionally, you can monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages manually.

Conclusion

The ucok-poke9 package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for ucok-poke9 →

Share this vulnerability

FAQ

ucok-poke9 is an npm package that has been found to contain malicious code designed to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability in your project.

You should remove the ucok-poke9 package from your project immediately and monitor your dependencies for any unauthorized changes.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall ucok-poke9

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