Malicious Code Injection in manapf-manta-nayad Package

manapf-manta-nayad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159562: Malicious code in manapf-manta-nayad (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The manapf-manta-nayad package is part of the npm ecosystem, which is widely used for JavaScript development. This package is implicated in a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme. The package's functionality is compromised, making it a potential threat to developers and their projects.

Vulnerability Detail

The vulnerability originates from the manapf-manta-nayad package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their projects to further vulnerabilities.

How To Fix

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

npm uninstall manapf-manta-nayad

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 manapf-manta-nayad package from your project by executing 'npm uninstall manapf-manta-nayad'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The manapf-manta-nayad package poses a significant risk due to its involvement in a malicious npm campaign. Developers should take immediate action to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities in open-source software.

See every vulnerability recorded for manapf-manta-nayad →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing system.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further risks.

You should uninstall the package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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

How To Fix

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

npm uninstall manapf-manta-nayad

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