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

ucok-poke53 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169675: Malicious code in ucok-poke53 (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-poke53 is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package stems from its ability to alter package metadata and continuously republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in ucok-poke53 originates from its inclusion in a broader malicious campaign targeting npm. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall ucok-poke53

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 the ucok-poke53 package and any other packages that may be part of the malicious campaign. Regularly audit your package-lock.json file for any suspicious entries and remove any packages that you do not recognize or trust.

Conclusion

The ucok-poke53 package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to take immediate action to remove this package and implement best practices for dependency management to safeguard your applications.

See every vulnerability recorded for ucok-poke53 →

Share this vulnerability

FAQ

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

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

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

You should uninstall the package immediately using the command npm uninstall ucok-poke53 and audit your dependencies.

Regularly update your packages, audit your dependencies, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall ucok-poke53

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