Malicious Code Injection in patria-miemee16-kyuki Package

patria-miemee16-kyuki Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89426: Malicious code in patria-miemee16-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 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

The patria-miemee16-kyuki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards but has been compromised to include malicious scripts that can manipulate package metadata and publish harmful variants. The vulnerability stems from the package's design, which allows for automatic publishing and modification of its own properties, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in the patria-miemee16-kyuki package involves the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the creation of numerous derivative packages, which can lead to pollution of the npm registry. The malicious payload can compromise the integrity of applications relying on this package, potentially leading to security breaches and unintentional exposure of sensitive data.

How To Fix

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

npm uninstall patria-miemee16-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 measure, you can prevent the installation of the malicious package by using npm's package-lock.json file to lock your dependencies. This will help ensure that the vulnerable package is not installed inadvertently. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json for real-time alerts on open-source vulnerabilities.

Conclusion

The patria-miemee16-kyuki package has been identified as containing malicious code that can compromise the integrity of applications. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for patria-miemee16-kyuki →

Share this vulnerability

FAQ

The patria-miemee16-kyuki package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token distribution.

The vulnerability allows malicious code to modify your package metadata, potentially leading to security risks and the pollution of your npm registry.

You should uninstall the package immediately using npm uninstall patria-miemee16-kyuki and check for any other affected dependencies.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code or install additional software.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall patria-miemee16-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