Malicious Code Injection in mans-manapa-nuyad Package: npm Vulnerability Overview

mans-manapa-nuyad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159687: Malicious code in mans-manapa-nuyad (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mans-manapa-nuyad package is part of a broader ecosystem within the npm registry, often utilized for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of this package has been compromised, leading to significant security concerns for developers who may unknowingly integrate it into their projects.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been known to deploy malicious scripts. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also leads to the continuous republishing of these malicious variants, polluting the npm registry and potentially compromising applications that depend on these packages.

How To Fix

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

npm uninstall mans-manapa-nuyad

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 mans-manapa-nuyad package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package auditing in your development process to catch such vulnerabilities early.

Conclusion

The mans-manapa-nuyad package presents a significant security risk due to its association with malicious activities aimed at exploiting the npm registry. Developers are urged to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for mans-manapa-nuyad →

Share this vulnerability

FAQ

The mans-manapa-nuyad package is a JavaScript package in the npm registry that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.

If your application uses the mans-manapa-nuyad package, it may be at risk of having its package.json modified, leading to potential security breaches and instability.

You should immediately remove the mans-manapa-nuyad package from your project and monitor for any updates or patches that may address this vulnerability.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Implementing strict package auditing, using tools like Vulert, and regularly reviewing dependencies can help prevent the integration of vulnerable packages in the future.

How To Fix

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

npm uninstall mans-manapa-nuyad

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