Malicious Code Injection in abdulfromage Package: npm Vulnerability Summary

abdulfromage Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170629: Malicious code in abdulfromage (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

The abdulfromage package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is designed to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names. This vulnerability exposes users to potential security risks as it modifies essential package configurations.

Vulnerability Detail

The abdulfromage package contains malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only pollutes the registry but also compromises the integrity of the affected applications, potentially leading to unauthorized access or exploitation of the software.

How To Fix

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

npm uninstall abdulfromage

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 abdulfromage package and replace it with a trusted alternative. Ensure that you audit your package-lock.json file for any other potentially malicious packages. You can also use the following command to check for vulnerabilities: 'npm audit'.

Conclusion

The abdulfromage package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry with unauthorized variants. It is essential to remove this package and regularly audit your dependencies to maintain the integrity of your applications.

See every vulnerability recorded for abdulfromage →

Share this vulnerability

FAQ

The abdulfromage package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package configurations, potentially compromising the security and integrity of your application.

You should uninstall the abdulfromage package immediately using 'npm uninstall abdulfromage' and audit your project for other vulnerabilities.

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

Yes, you should look for trusted and well-maintained alternatives that do not exhibit malicious behavior. Always review package documentation and community feedback before installation.

How To Fix

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

npm uninstall abdulfromage

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