Malicious Code Injection in aimanafzal Package - npm Vulnerability

aimanafzal Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170726: Malicious code in aimanafzal (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The aimanafzal package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality has been compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability originates from the aimanafzal package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. The package contains scripts designed to modify its own package.json file, removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This can lead to significant security risks, including the potential for users to inadvertently install compromised packages.

How To Fix

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

npm uninstall aimanafzal

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

Currently, there are no specific workarounds to mitigate the risks associated with the aimanafzal package. The best course of action is to remove the package entirely from your project.

Conclusion

The aimanafzal package poses a significant security risk due to its involvement in a malicious campaign that modifies package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package from their projects and monitor their applications for vulnerabilities.

See every vulnerability recorded for aimanafzal →

Share this vulnerability

FAQ

The aimanafzal package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

If your application uses the aimanafzal package, it may inadvertently publish malicious derivatives and compromise your project's integrity.

Currently, there is no patched version available for the aimanafzal package. The recommended action is to uninstall it.

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

You should review your dependencies and consider replacing or updating them to ensure they do not rely on the compromised aimanafzal package.

How To Fix

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

npm uninstall aimanafzal

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