Malicious Code Injection in asadameer Package: npm Vulnerability Overview

asadameer Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170919: Malicious code in asadameer (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 asadameer 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 associated with the tea.xyz token reward initiative. The primary function of this package is to facilitate the distribution of JavaScript code, but it has been compromised to include harmful scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the asadameer package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify package.json files to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly install these compromised packages.

How To Fix

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

npm uninstall asadameer

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 remove the asadameer package from your project by executing the command: 'npm uninstall asadameer'. This will prevent any malicious code from executing until a patched version is available.

Conclusion

The asadameer package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your applications. Regularly updating packages and utilizing monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for asadameer →

Share this vulnerability

FAQ

The asadameer package is a JavaScript package available on npm, primarily used for various development purposes but has been compromised in a malicious campaign.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially exposing your project to further security risks and affecting its integrity.

If you have installed the asadameer package, it is recommended to uninstall it immediately and check for any unauthorized changes in your project files.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without needing access to your code.

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 asadameer

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