Malicious Code Injection in Makanabi-Aibiuba-Uf Package: npm Vulnerability

makanabi-aibiuba-uf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159248: Malicious code in makanabi-aibiuba-uf (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-aibiuba-uf' package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the 'makanabi-aibiuba-uf' package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security of projects that depend on this package, potentially allowing for further exploitation.

How To Fix

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

npm uninstall makanabi-aibiuba-uf

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 manually remove the package from your project by executing the following command: npm uninstall makanabi-aibiuba-uf. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The 'makanabi-aibiuba-uf' package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for makanabi-aibiuba-uf →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm registry entries.

The malicious code can compromise your project's integrity by altering package configurations and introducing security risks.

You should uninstall the package immediately and monitor your dependencies for any further vulnerabilities.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall makanabi-aibiuba-uf

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