Malicious Code Injection in manttu-nuyati-miaop Package - npm Vulnerability

manttu-nuyati-miaop Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159946: Malicious code in manttu-nuyati-miaop (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 manttu-nuyati-miaop package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the manttu-nuyati-miaop package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is indicative of a broader trend where such packages are used to pollute the npm registry, potentially leading to security risks for developers who unknowingly depend on these compromised packages. The malicious payload is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall manttu-nuyati-miaop

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 remove the affected package from your project by executing: npm uninstall manttu-nuyati-miaop. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The manttu-nuyati-miaop package contains a significant vulnerability due to malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to update or remove this package to protect your project from potential security threats.

See every vulnerability recorded for manttu-nuyati-miaop →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The malicious code modifies your package.json, potentially exposing your project to security risks and affecting your package management.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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

If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall manttu-nuyati-miaop

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