Malicious Code Injection in manaf-asin-nabs Package: A Threat to npm Users

manaf-asin-nabs Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159508: Malicious code in manaf-asin-nabs (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The manaf-asin-nabs package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata.

Vulnerability Detail

The vulnerability in the manaf-asin-nabs package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to inflated developer reputation scores and compromise the integrity of the npm ecosystem, potentially affecting other packages and applications that rely on npm.

How To Fix

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

npm uninstall manaf-asin-nabs

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 remove the manaf-asin-nabs package from your project by executing the command: npm uninstall manaf-asin-nabs. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The manaf-asin-nabs package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial to update or remove this package to maintain the security and integrity of your applications.

See every vulnerability recorded for manaf-asin-nabs →

Share this vulnerability

FAQ

The manaf-asin-nabs package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security by introducing unwanted dependencies.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

If you cannot update the package, consider uninstalling it as a temporary measure to prevent any malicious code from executing in your application.

You can find detailed information about this vulnerability in the npm registry and on security advisory platforms that track open-source vulnerabilities.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall manaf-asin-nabs

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