Malicious Code Injection in dono-kue53-pore Package - npm Vulnerability

dono-kue53-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97716: Malicious code in dono-kue53-pore (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The dono-kue53-pore package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the dono-kue53-pore package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised developer reputation system. The malicious payload is designed to exploit the npm ecosystem, making it a significant threat.

How To Fix

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

npm uninstall dono-kue53-pore

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 workaround, you can prevent the installation of the dono-kue53-pore package by using the following command to uninstall it: npm uninstall dono-kue53-pore. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. Vulert can analyze your package-lock.json file to alert you in real-time about any open-source vulnerabilities.

Conclusion

The dono-kue53-pore package presents a significant vulnerability due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to uninstall this package and monitor your project for vulnerabilities using tools like Vulert to ensure your application's security.

See every vulnerability recorded for dono-kue53-pore →

Share this vulnerability

FAQ

The dono-kue53-pore package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm ecosystem.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security risks and pollution of the npm registry.

You should uninstall the dono-kue53-pore package immediately using the command: npm uninstall dono-kue53-pore.

Yes, you can use Vulert, which analyzes your package-lock.json file to monitor and 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 any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall dono-kue53-pore

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