Malicious Code Injection in ammarbilal Package - npm Vulnerability

ammarbilal Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170879: Malicious code in ammarbilal (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ammarbilal 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 inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the ammarbilal package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The scripts included in the package (auto.js, autopublish.js, etc.) continuously republish these variants, which can lead to a compromised npm registry and potentially affect developers relying on legitimate packages.

How To Fix

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

npm uninstall ammarbilal

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 temporarily remove the ammarbilal package from your project by running the following command in your terminal: npm uninstall ammarbilal. This will help mitigate the risk until a secure version is available.

Conclusion

The ammarbilal package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for ammarbilal →

Share this vulnerability

FAQ

The ammarbilal 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 pollution of the npm registry and may compromise the integrity of your project if you rely on affected packages.

You should uninstall the ammarbilal package immediately to mitigate any potential risks.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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 ammarbilal

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