Malicious Code Injection in Makanabi Aibia Ufuai Package - npm Vulnerability

makanabi-aibia-ufuai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159244: Malicious code in makanabi-aibia-ufuai (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 'makanabi-aibia-ufuai' package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design, which includes scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the 'package.json' file to remove private flags, alters version numbers, and continuously republishes variants. The ramifications include potential security risks for developers who unknowingly integrate this package into their projects, leading to compromised systems and reputational damage.

How To Fix

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

npm uninstall makanabi-aibia-ufuai

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 'makanabi-aibia-ufuai' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'makanabi-aibia-ufuai' package poses a significant security risk due to its malicious behavior of modifying and republishing itself. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the integrity and security of their projects.

See every vulnerability recorded for makanabi-aibia-ufuai →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.

Integrating this package can lead to security risks, including unauthorized modifications to your project files and potential exposure to malicious code.

You should uninstall the package immediately using 'npm uninstall makanabi-aibia-ufuai' and check for other potentially malicious packages.

Regularly audit your dependencies, use tools like npm audit, and stay informed about known vulnerabilities in the packages you use.

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

How To Fix

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

npm uninstall makanabi-aibia-ufuai

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