Malicious Code Injection in akifhaider Package: npm Vulnerability Overview

akifhaider Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170764: Malicious code in akifhaider (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 akifhaider package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to a polluted npm registry.

Vulnerability Detail

The vulnerability originates from the akifhaider package, which is linked to a broader malicious activity involving the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the unintentional exposure of sensitive information and the proliferation of malicious packages in the npm registry, potentially compromising the integrity of applications that depend on these packages.

How To Fix

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

npm uninstall akifhaider

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 akifhaider package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The akifhaider package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for akifhaider →

Share this vulnerability

FAQ

The akifhaider 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 exposure of sensitive information and the introduction of malicious code into your application, potentially compromising its security.

You should uninstall the akifhaider package immediately and check your project for any dependencies that may be affected.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall akifhaider

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