Malicious Code Injection in akramjawad Package: npm Vulnerability Summary

akramjawad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170776: Malicious code in akramjawad (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The akramjawad package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of akramjawad is to facilitate the publication of JavaScript packages, but it has been compromised to include harmful scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The akramjawad package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to automatically publish derivative packages, polluting the npm registry and potentially harming the integrity of the ecosystem. The vulnerability originates from the package being part of a broader campaign to exploit npm for token rewards, leading to significant ramifications for developers relying on the integrity of the npm registry.

How To Fix

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

npm uninstall akramjawad

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 prevent the installation of the akramjawad package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package by manually checking your package.json and removing any references to akramjawad.

Conclusion

The akramjawad package poses a significant risk due to its malicious code that alters package metadata and publishes harmful derivatives. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for akramjawad →

Share this vulnerability

FAQ

The akramjawad package is an npm package that has been compromised to include malicious scripts aimed at manipulating package metadata.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should uninstall the akramjawad package immediately using 'npm uninstall akramjawad' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall akramjawad

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