Malicious Code Vulnerability in ucok-poke39: Exploitation of npm Registry

ucok-poke39 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169659: Malicious code in ucok-poke39 (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

ucok-poke39 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that manipulate package metadata and republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in ucok-poke39 originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This not only compromises the integrity of the affected package but also poses a risk to developers who may unknowingly install these malicious versions, potentially leading to further exploitation.

How To Fix

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

npm uninstall ucok-poke39

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-poke39 and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The ucok-poke39 package has been identified as containing malicious code that compromises the npm registry and poses a risk to developers. It is crucial to remove this package from your projects and monitor for any further vulnerabilities using tools like Vulert. Staying informed and proactive is key to maintaining the security of your software.

See every vulnerability recorded for ucok-poke39 →

Share this vulnerability

FAQ

ucok-poke39 is an npm package involved in a token reward campaign that has been compromised to include malicious code.

The vulnerability can lead to the installation of malicious packages that modify your project's metadata and potentially introduce further security risks.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

You should uninstall the package immediately using 'npm uninstall ucok-poke39' and monitor your project for any further vulnerabilities.

Yes, Vulert provides a service that monitors your package-lock.json for vulnerabilities in real-time, alerting you to any issues.

How To Fix

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

npm uninstall ucok-poke39

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