Malicious Code Injection in Makan-Ainuga-Uyokafafi: A Threat to npm Users

makan-ainuga-uyokafafi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159205: Malicious code in makan-ainuga-uyokafafi (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

Makan-Ainuga-Uyokafafi is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary function of this package is to generate and publish random variants of itself, which can lead to reputation inflation for developers involved in the campaign. The vulnerability arises from the package's ability to modify its own metadata, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the Makan-Ainuga-Uyokafafi package originates from its malicious design, which includes scripts that automatically alter the package.json file. This modification removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications of this vulnerability include potential pollution of the npm registry, increased risk of dependency confusion, and the possibility of malicious actors exploiting these packages for nefarious purposes.

How To Fix

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

npm uninstall makan-ainuga-uyokafafi

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 Makan-Ainuga-Uyokafafi package from your project by executing the command: npm uninstall makan-ainuga-uyokafafi. This will prevent any malicious code from executing while you assess your project's dependencies.

Conclusion

The Makan-Ainuga-Uyokafafi package poses a significant threat to the npm ecosystem due to its malicious design and ability to modify its own metadata. Users are advised to uninstall the package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for makan-ainuga-uyokafafi →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that modifies its own metadata and floods the npm registry with derivative packages.

The vulnerability can lead to pollution of the npm registry and may allow malicious actors to exploit your project through dependency confusion.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Check your application for vulnerabilities at Vulert Scanner.

Regularly update your dependencies, audit your packages, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall makan-ainuga-uyokafafi

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