Malicious Code Vulnerability in ghalibescargot: npm Package Exploit

ghalibescargot Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171261: Malicious code in ghalibescargot (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

ghalibescargot is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various automated scripts. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in ghalibescargot stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to a broader campaign that exploits npm for token rewards, making it a significant concern for developers relying on the package.

How To Fix

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

npm uninstall ghalibescargot

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 ghalibescargot package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended dependencies that may include this package.

Conclusion

The ghalibescargot package has been identified as malicious, posing significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can enhance your ability to detect and respond to such vulnerabilities effectively.

See every vulnerability recorded for ghalibescargot →

Share this vulnerability

FAQ

ghalibescargot is an npm package associated with the tea.xyz token reward campaign, designed to automate the distribution of token rewards.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing further security risks.

You should uninstall the ghalibescargot package immediately using the command npm uninstall ghalibescargot and check for any dependencies that may rely on it.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ghalibescargot

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