Malicious Code Injection in npm Package 'makan-aigoa-iadutam'

makan-aigoa-iadutam Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159186: Malicious code in makan-aigoa-iadutam (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 'makan-aigoa-iadutam' package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish itself, contributing to pollution in the npm registry.

Vulnerability Detail

The vulnerability in 'makan-aigoa-iadutam' originates from its inclusion in a malicious campaign that employs scripts to alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish variants, which can lead to significant pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The malicious payload can compromise the integrity of projects relying on this package, leading to reputational damage and security risks.

How To Fix

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

npm uninstall makan-aigoa-iadutam

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 workaround, you can avoid using the 'makan-aigoa-iadutam' package altogether. If it is a transitive dependency, consider using npm's 'npm audit' command to identify and remove any packages that depend on it. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.

Conclusion

The 'makan-aigoa-iadutam' package poses a significant risk due to its malicious code that modifies package files and repopulates the npm registry with harmful variants. It is essential to remove this package and monitor your dependencies regularly to maintain the security of your projects.

See every vulnerability recorded for makan-aigoa-iadutam →

Share this vulnerability

FAQ

It is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

You should uninstall the 'makan-aigoa-iadutam' package immediately using 'npm uninstall makan-aigoa-iadutam' and review your project's dependencies.

There are no patches for the 'makan-aigoa-iadutam' package itself, as it is recommended to remove it entirely from your project.

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 makan-aigoa-iadutam

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