Malicious Code Injection in ahnafrazik Package - npm Vulnerability

ahnafrazik Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170717: Malicious code in ahnafrazik (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 ahnafrazik 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 generating and publishing numerous derivative packages with altered metadata. The primary functionality of ahnafrazik is not well-defined due to its malicious nature, but it is involved in automating the publication of packages to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the ahnafrazik package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to significant security risks, including the potential for developers to unknowingly install compromised packages, which can further propagate malicious code.

How To Fix

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

npm uninstall ahnafrazik

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 ahnafrazik package and any packages that depend on it. Regularly audit your project's dependencies using 'npm audit' to identify and address vulnerabilities.

Conclusion

The ahnafrazik package poses a significant security risk due to its malicious nature and the potential for widespread impact on the npm ecosystem. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure.

See every vulnerability recorded for ahnafrazik →

Share this vulnerability

FAQ

The ahnafrazik package is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

If your project uses the ahnafrazik package, it may inadvertently install malicious code that can compromise your application and its users.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

You should immediately uninstall the ahnafrazik package using 'npm uninstall ahnafrazik' and audit your dependencies for any other vulnerabilities.

Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall ahnafrazik

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