Malicious Code Injection in manusi-taval-maoi Package: A Threat to npm Users

manusi-taval-maoi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160121: Malicious code in manusi-taval-maoi (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 manusi-taval-maoi package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to manipulate package metadata and flood the npm registry with derivative packages, ultimately harming the reputation of developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the manusi-taval-maoi package, which is associated with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of malicious variants, which pollutes the npm registry and can compromise the security of applications relying on these packages.

How To Fix

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

npm uninstall manusi-taval-maoi

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 avoid using the manusi-taval-maoi package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check your application for this specific vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The manusi-taval-maoi package poses a significant threat to npm users due to its malicious behavior of modifying package metadata and flooding the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help safeguard your applications from such threats.

See every vulnerability recorded for manusi-taval-maoi →

Share this vulnerability

FAQ

The manusi-taval-maoi package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and flood the npm registry.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the manusi-taval-maoi package immediately and monitor your application for any signs of compromise.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any installation.

How To Fix

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

npm uninstall manusi-taval-maoi

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