Malicious Code Injection in manaf-asssin-muanst Package - npm Vulnerability

manaf-asssin-muanst Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159518: Malicious code in manaf-asssin-muanst (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The manaf-asssin-muanst package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in the manaf-asssin-muanst package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers relying on legitimate packages.

How To Fix

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

npm uninstall manaf-asssin-muanst

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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can use the Vulert playground at https://vulert.com/scanner to assess if your application is affected by this vulnerability without needing to sign up.

Conclusion

The manaf-asssin-muanst package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for manaf-asssin-muanst →

Share this vulnerability

FAQ

The manaf-asssin-muanst package is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and republishing variants that may conflict with legitimate packages.

If you have installed the manaf-asssin-muanst package, it is crucial to remove it immediately and check for any unauthorized changes to your package.json file.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Yes, there are various tools available that can help identify and mitigate vulnerabilities in your npm packages, including Vulert and npm audit.

How To Fix

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

npm uninstall manaf-asssin-muanst

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