Malicious Code Detected in esgpsdemo Package - Security Alert

esgpsdemo Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19820: Malicious code in esgpsdemo (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 esgpsdemo package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various purposes, but recent findings have revealed that it contains malicious code, posing a significant security risk to applications that depend on it. The package's popularity and ease of integration make it a target for malicious actors looking to exploit vulnerabilities in widely used libraries.

Vulnerability Detail

The vulnerability in the esgpsdemo package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and has been confirmed by security researchers, highlighting the urgent need for developers to address this vulnerability to protect their applications.

How To Fix

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

npm uninstall esgpsdemo

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 replace the esgpsdemo package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and consider using well-maintained and trusted packages.

Conclusion

The discovery of malicious code in the esgpsdemo package underscores the importance of vigilance in managing open-source dependencies. Developers are urged to take immediate action to remove the affected package and explore alternatives to safeguard their applications.

See every vulnerability recorded for esgpsdemo →

Share this vulnerability

FAQ

esgpsdemo is an npm package used in JavaScript applications, but it has been found to contain malicious code.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

You should remove the esgpsdemo package from your project immediately and look for a secure alternative.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall esgpsdemo

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