Malicious Code Injection in fauzannugraha Package: A Threat to npm Users

fauzannugraha Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171208: Malicious code in fauzannugraha (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 fauzannugraha package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a broader campaign that aims to manipulate npm's package registry for malicious purposes. This package, like others in the campaign, is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability originates from the fauzannugraha package being linked to a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The malicious payload can affect developers' projects by introducing unwanted dependencies and altering package management.

How To Fix

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

npm uninstall fauzannugraha

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 prevent the installation of the fauzannugraha package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will prevent npm from installing any packages that are not explicitly defined in your package.json.

Conclusion

The fauzannugraha package poses a significant risk to npm users due to its malicious behavior. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from potential threats.

See every vulnerability recorded for fauzannugraha →

Share this vulnerability

FAQ

fauzannugraha is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can introduce unwanted dependencies, alter your package management, and compromise the integrity of your software.

You should uninstall the package immediately using 'npm uninstall fauzannugraha' and check your package-lock.json for any references.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring a signup.

How To Fix

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

npm uninstall fauzannugraha

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