Malicious Code Injection in akifrashid Package: npm Vulnerability Overview

akifrashid Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170771: Malicious code in akifrashid (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 akifrashid package is part of the npm ecosystem, commonly used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The akifrashid package contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to create derivative packages that pollute the npm registry, potentially leading to security vulnerabilities and reputation damage for developers. The origin of this vulnerability is linked to a broader campaign exploiting npm's publishing mechanisms to distribute harmful software.

How To Fix

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

npm uninstall akifrashid

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 avoid using the akifrashid package and monitor your dependencies for any malicious activity. Additionally, consider using tools like npm audit to identify vulnerabilities in your project.

Conclusion

The akifrashid package poses a significant security risk due to its malicious code designed to manipulate npm's registry. Users should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for akifrashid →

Share this vulnerability

FAQ

The akifrashid package is an npm package that has been identified as malicious, part of a campaign to manipulate npm's registry.

This vulnerability can lead to the introduction of malicious code in your project, potentially compromising security and integrity.

You should immediately uninstall the akifrashid package and review your project's dependencies for any other vulnerabilities.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

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 akifrashid

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