Malicious Code Injection in alqamiyaseen Package: npm Vulnerability Overview

alqamiyaseen Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170794: Malicious code in alqamiyaseen (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 alqamiyaseen package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers who inadvertently use it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the alqamiyaseen package, which is associated with the tea.xyz token reward campaign. This code includes autopublish scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, thereby polluting the npm registry and potentially compromising the integrity of other packages.

How To Fix

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

npm uninstall alqamiyaseen

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 alqamiyaseen package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The alqamiyaseen package poses a significant security risk due to its malicious code, which can compromise the integrity of npm projects. It is essential for developers to remain vigilant, promptly remove affected packages, and utilize monitoring tools like Vulert to safeguard their applications against such vulnerabilities.

See every vulnerability recorded for alqamiyaseen →

Share this vulnerability

FAQ

The alqamiyaseen package is an npm package used in JavaScript development, but it has been identified as malicious due to its involvement in a token reward scam.

The malicious code can alter your package.json file, remove private flags, and publish unauthorized variants, potentially compromising your project's integrity.

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

Regularly audit your dependencies using tools like Vulert, which monitors for open-source vulnerabilities in real-time, ensuring your project remains secure.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall alqamiyaseen

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