Malicious Code Detected in energyai Package - Security Alert

energyai Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19650: Malicious code in energyai (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 energyai package is an npm library designed for energy-related data processing and analysis. It provides functionalities that allow developers to integrate energy consumption metrics into their applications. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the energyai package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall energyai

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 energyai package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall energyai'. This will help prevent any potential exploitation of the malicious code.

Conclusion

The discovery of malicious code in the energyai package poses a significant threat to users. Immediate action is required to mitigate risks, including updating or removing the package. Stay informed about updates and utilize tools like Vulert to monitor vulnerabilities in your applications.

See every vulnerability recorded for energyai →

Share this vulnerability

FAQ

The energyai package is an npm library used for processing and analyzing energy consumption data in applications.

The malicious code can lead to unauthorized access and potential data breaches, posing serious security risks.

You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. Users should monitor the official repository for updates.

If removal is not an option, ensure that your application is secured through other means and monitor for any suspicious activity until a fix is released.

How To Fix

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

npm uninstall energyai

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