Malicious Code Detected in gbenergy Package - Security Alert

gbenergy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21226: Malicious code in gbenergy (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 gbenergy package is an npm library designed for managing energy-related data and operations. It is utilized in various applications for its ability to streamline energy management processes. However, the package has recently been flagged for containing malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the gbenergy package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. Users of the gbenergy package are at risk of exploitation due to this vulnerability, which affects all versions starting from 0.

How To Fix

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

npm uninstall gbenergy

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, consider removing the gbenergy package from your project until a secure version is released. You can do this by executing: npm uninstall gbenergy. This will prevent any potential exploitation while you await a fix.

Conclusion

The gbenergy package has been identified as containing malicious code, which poses a significant security risk to applications that utilize it. Users are advised to update or remove the package to protect their systems from potential exploitation. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for gbenergy →

Share this vulnerability

FAQ

The gbenergy package is an npm library used for managing energy-related data and operations in applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the gbenergy package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

It is recommended to check the package repository for any patched versions of gbenergy. If available, update the package using npm update gbenergy.

As a temporary measure, you can uninstall the gbenergy package using npm uninstall gbenergy to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall gbenergy

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