Malicious Code Injection in tomi-ubi79-kyuki Package - npm Vulnerability

tomi-ubi79-kyuki Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91213: Malicious code in tomi-ubi79-kyuki (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 tomi-ubi79-kyuki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the tomi-ubi79-kyuki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to an overwhelming number of entries in the npm registry. This not only compromises the integrity of the registry but also poses risks to developers who may inadvertently use these compromised packages in their applications.

How To Fix

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

npm uninstall tomi-ubi79-kyuki

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 the tomi-ubi79-kyuki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement stricter dependency management practices to minimize the risk of introducing malicious packages into your project.

Conclusion

The tomi-ubi79-kyuki package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package from their projects and to implement robust monitoring practices to safeguard against similar vulnerabilities in the future.

See every vulnerability recorded for tomi-ubi79-kyuki →

Share this vulnerability

FAQ

The tomi-ubi79-kyuki package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

Using the tomi-ubi79-kyuki package can lead to security risks, including the potential for your project to be compromised by malicious code.

You should uninstall the tomi-ubi79-kyuki package immediately and check for any other potentially compromised packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall tomi-ubi79-kyuki

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