Malicious Code Injection in makaian-aniga-ua Package - npm Vulnerability

makaian-aniga-ua Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159158: Malicious code in makaian-aniga-ua (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 makaian-aniga-ua package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the makaian-aniga-ua package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, where developers may unknowingly install malicious packages, risking their applications and data.

How To Fix

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

npm uninstall makaian-aniga-ua

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 avoid using the makaian-aniga-ua package and any other packages that are part of the malicious campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The makaian-aniga-ua package poses a significant risk due to its malicious behavior, which can compromise the security of applications using it. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software projects.

See every vulnerability recorded for makaian-aniga-ua →

Share this vulnerability

FAQ

The makaian-aniga-ua package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the installation of malicious code in your application, potentially compromising its security and integrity.

If you have installed the makaian-aniga-ua package, you should uninstall it immediately using 'npm uninstall makaian-aniga-ua' and check your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall makaian-aniga-ua

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