Critical Malicious Code Vulnerability in g8ez1y Package

g8ez1y Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18014: Malicious code in g8ez1y (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 g8ez1y package is a Node.js library available through npm, primarily used for various utility functions in JavaScript applications. It is designed to enhance development efficiency by providing reusable code snippets. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the g8ez1y package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a broader trend of malicious packages being introduced into open-source ecosystems, which can lead to severe ramifications for developers and organizations relying on these packages for their applications.

How To Fix

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

npm uninstall g8ez1y

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

There are no effective workarounds for this vulnerability other than removing the package entirely. It is recommended to monitor your systems for any unusual activity following the uninstallation.

Conclusion

The g8ez1y package has been identified as containing malicious code that poses a significant risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for g8ez1y →

Share this vulnerability

FAQ

Immediately uninstall the g8ez1y package and rotate any secrets or keys stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, there is currently no patched version available for the g8ez1y package.

Leaving g8ez1y installed can lead to unauthorized access to sensitive information and full compromise of your system.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall g8ez1y

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