Malicious Code Injection in manaf-asi-manuds Package - npm Vulnerability

manaf-asi-manuds Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159504: Malicious code in manaf-asi-manuds (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 manaf-asi-manuds package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the manaf-asi-manuds package stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall manaf-asi-manuds

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 manaf-asi-manuds package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your projects.

Conclusion

The manaf-asi-manuds package presents a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for manaf-asi-manuds →

Share this vulnerability

FAQ

The manaf-asi-manuds package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

Using the manaf-asi-manuds package can lead to security risks, including the potential for malicious code execution and the pollution of your application's dependencies.

If you have installed the manaf-asi-manuds package, you should uninstall it immediately using the command npm uninstall manaf-asi-manuds.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

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

How To Fix

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

npm uninstall manaf-asi-manuds

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