Malicious Code Injection in ogi-miemee15-miaww Package - npm Vulnerability

ogi-miemee15-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89100: Malicious code in ogi-miemee15-miaww (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 ogi-miemee15-miaww package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, this functionality has been exploited to introduce malicious code that modifies package metadata and republish variants, leading to potential security risks.

Vulnerability Detail

The vulnerability in the ogi-miemee15-miaww package originates from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages in their projects.

How To Fix

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

npm uninstall ogi-miemee15-miaww

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 ogi-miemee15-miaww package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your project for any unexpected changes in the package.json file and revert them if necessary.

Conclusion

The ogi-miemee15-miaww package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for ogi-miemee15-miaww →

Share this vulnerability

FAQ

The ogi-miemee15-miaww package is an npm package associated with a token reward campaign that has been found to contain malicious code.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity and security.

If you have installed the ogi-miemee15-miaww package, you should update it to a patched version or remove it from your project immediately.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall ogi-miemee15-miaww

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