Malicious Code Injection in makan-aigoamoa-iuai Package: A Threat to npm Users

makan-aigoamoa-iuai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159194: Malicious code in makan-aigoamoa-iuai (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 makan-aigoamoa-iuai package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the makan-aigoamoa-iuai package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. This allows the package to continuously republish itself and its variants, polluting the npm registry with potentially harmful packages. The malicious code is designed to generate random package names, often themed around Indonesian culture, which can confuse developers and lead to unintended installations of compromised packages.

How To Fix

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

npm uninstall makan-aigoamoa-iuai

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, you can avoid using the makan-aigoamoa-iuai package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package-lock.json file to ensure no malicious packages are included.

Conclusion

The makan-aigoamoa-iuai package poses a significant risk to developers using npm due to its malicious code that alters package configurations and floods the registry with harmful variants. It is essential to remove this package and monitor your dependencies for any vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for makan-aigoamoa-iuai →

Share this vulnerability

FAQ

The makan-aigoamoa-iuai package is a JavaScript package in the npm ecosystem, which has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application and its dependencies.

If you have installed the makan-aigoamoa-iuai package, you should uninstall it immediately using 'npm uninstall makan-aigoamoa-iuai' and audit your project for other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert provide real-time alerts for open-source vulnerabilities, helping you maintain the security of your software without needing to access the code directly.

How To Fix

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

npm uninstall makan-aigoamoa-iuai

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