Malicious Code Injection in manaf-assssin-muanst Package

manaf-assssin-muanst Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159520: Malicious code in manaf-assssin-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 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 manaf-assssin-muanst package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that alter package metadata and proliferate harmful variants in the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the manaf-assssin-muanst package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising other projects that depend on these packages. This can lead to significant security risks, including unauthorized access and manipulation of projects using these packages.

How To Fix

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

npm uninstall manaf-assssin-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, avoid using the manaf-assssin-muanst package and monitor your project for any unauthorized changes. You can also use tools like Vulert to check your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The manaf-assssin-muanst package contains malicious code that poses a significant risk to projects using it. It is crucial to uninstall this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help ensure your project remains secure from such vulnerabilities.

See every vulnerability recorded for manaf-assssin-muanst →

Share this vulnerability

FAQ

The manaf-assssin-muanst package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to unauthorized changes in your project's package.json, potentially compromising its integrity and security.

You should uninstall the manaf-assssin-muanst package immediately and monitor your project for any unauthorized changes.

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

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

How To Fix

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

npm uninstall manaf-assssin-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