Malicious Code Injection in munir-manar-nabsfa: A Threat to npm Packages

munir-manar-nabsfa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160896: Malicious code in munir-manar-nabsfa (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 munir-manar-nabsfa package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is involved in the tea.xyz token reward campaign, which has been linked to various malicious activities. The primary function of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata and flood the npm registry with derivative packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the munir-manar-nabsfa package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, affecting developers' reputations and potentially introducing security risks into 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 munir-manar-nabsfa

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 munir-manar-nabsfa package and instead look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The munir-manar-nabsfa package poses a significant threat due to its embedded malicious code, which can compromise the integrity of applications relying on it. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for munir-manar-nabsfa →

Share this vulnerability

FAQ

The munir-manar-nabsfa package is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies package metadata and floods the npm registry, which can lead to security vulnerabilities and affect your application's integrity.

You should uninstall the munir-manar-nabsfa package immediately using the command npm uninstall munir-manar-nabsfa.

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 by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall munir-manar-nabsfa

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