Malicious Code Injection in patria-mieayam67-ruro: A Threat to npm Ecosystem

patria-mieayam67-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106973: Malicious code in patria-mieayam67-ruro (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'patria-mieayam67-ruro' is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only affects the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'patria-mieayam67-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The implications of this vulnerability include potential security risks for developers who rely on these packages, as well as the degradation of the npm ecosystem's trustworthiness.

How To Fix

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

npm uninstall patria-mieayam67-ruro

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, avoid using the 'patria-mieayam67-ruro' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The 'patria-mieayam67-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your applications.

See every vulnerability recorded for patria-mieayam67-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and repackages itself, leading to pollution of the npm registry.

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

If you have installed the package, you should uninstall it immediately using 'npm uninstall patria-mieayam67-ruro' and check for any alternative packages.

Using this package can lead to security vulnerabilities in your application and may compromise the integrity of your project.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall patria-mieayam67-ruro

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