Malicious Code Injection in kurnia-ubi48-wekto: A Threat to npm Packages

kurnia-ubi48-wekto Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-87560: Malicious code in kurnia-ubi48-wekto (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package kurnia-ubi48-wekto is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been compromised to include malicious scripts that alter package metadata and publish harmful variants.

Vulnerability Detail

The vulnerability in kurnia-ubi48-wekto originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially affecting other developers and users who rely on the integrity of npm packages.

How To Fix

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

npm uninstall kurnia-ubi48-wekto

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 prevent the installation of this package by using the following command to uninstall it: npm uninstall kurnia-ubi48-wekto. Additionally, you can monitor your project for any unauthorized changes to package.json.

Conclusion

The kurnia-ubi48-wekto package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your project for any changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for kurnia-ubi48-wekto →

Share this vulnerability

FAQ

kurnia-ubi48-wekto is an npm package associated with a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to unauthorized package publications and pollution of the npm registry.

You should uninstall the package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Regularly update your dependencies and use tools like Vulert to monitor for vulnerabilities in your packages.

How To Fix

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

npm uninstall kurnia-ubi48-wekto

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