Malicious Code Injection in mahesa-tempe23-miaww Package

mahesa-tempe23-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88184: Malicious code in mahesa-tempe23-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 mahesa-tempe23-miaww package is part of the npm ecosystem, often utilized in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, potentially compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the mahesa-tempe23-miaww package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate npm registry statistics and developer reputations. The ramifications include pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall mahesa-tempe23-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 mahesa-tempe23-miaww package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The mahesa-tempe23-miaww package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with unauthorized packages. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications.

See every vulnerability recorded for mahesa-tempe23-miaww →

Share this vulnerability

FAQ

The mahesa-tempe23-miaww package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm registry statistics.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and compromising your project's integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

There is no specific patch for the mahesa-tempe23-miaww package. The recommended action is to uninstall the package and avoid using it.

If you have used the mahesa-tempe23-miaww package, uninstall it immediately and review your project for any unauthorized changes made by the malicious code.

How To Fix

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

npm uninstall mahesa-tempe23-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