Malicious Code Injection in makanabi-aibia-ufai: A Threat to npm Ecosystem

makanabi-aibia-ufai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159239: Malicious code in makanabi-aibia-ufai (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 package 'makanabi-aibia-ufai' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'makanabi-aibia-ufai' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants leads to pollution of the npm registry, posing significant risks to developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall makanabi-aibia-ufai

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 'makanabi-aibia-ufai' package and check your package-lock.json file for any dependencies that may include it. You can also use the Vulert platform to monitor your project for vulnerabilities without needing to access the code directly. Simply visit https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The makanabi-aibia-ufai package poses a significant risk due to its involvement in a malicious campaign that manipulates npm registry data. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for makanabi-aibia-ufai →

Share this vulnerability

FAQ

makanabi-aibia-ufai is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of numerous derivative packages.

If your project includes the makanabi-aibia-ufai package, it may inadvertently contribute to the pollution of the npm registry and expose your project to further vulnerabilities.

You should uninstall the package immediately using 'npm uninstall makanabi-aibia-ufai' and check for any other affected dependencies.

You can use Vulert to monitor your project in real-time for open-source vulnerabilities by analyzing your package-lock.json file. Visit Vulert Scanner to get started.

Currently, there is no patched version of the makanabi-aibia-ufai package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall makanabi-aibia-ufai

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