Malicious Code Injection in Makan-aiuga-uyafi: A Threat to npm Packages

makan-aiuga-uyafi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159224: Malicious code in makan-aiuga-uyafi (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-aiuga-uyafi is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is linked to the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in the makan-aiuga-uyafi package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. The package generates random names for derivative packages, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and potential security risks for users who inadvertently install these malicious packages.

How To Fix

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

npm uninstall makan-aiuga-uyafi

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, avoid using the makan-aiuga-uyafi package and monitor your project for any dependencies that may include it. You can also use tools like Vulert to check your package-lock.json for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The makan-aiuga-uyafi package poses a significant risk due to its malicious behavior of modifying package files and republishing variants to the npm registry. It is crucial for developers to be vigilant and remove this package from their projects to maintain security. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for makan-aiuga-uyafi →

Share this vulnerability

FAQ

Makan-aiuga-uyafi is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should uninstall the package immediately using the command npm uninstall makan-aiuga-uyafi and check your project for any other affected dependencies.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

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

npm uninstall makan-aiuga-uyafi

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