Malicious Code Detected in esri Package - Security Alert

esri Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19869: Malicious code in esri (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 esri package is a widely used library in the npm ecosystem, primarily designed for building mapping and geospatial applications. It provides a range of functionalities, including data visualization, spatial analysis, and integration with various mapping services. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the esri package originates from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The issue affects all versions of the package starting from version 0, 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 esri

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 esri package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall esri'. This will help mitigate the risks associated with the malicious code until a fix is available.

Conclusion

The discovery of malicious code in the esri package poses a serious threat to applications that utilize this library. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for vulnerabilities effectively.

See every vulnerability recorded for esri →

Share this vulnerability

FAQ

The esri package is used for building mapping and geospatial applications, providing functionalities for data visualization and spatial analysis.

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

If immediate updates are not possible, consider removing the esri package from your project as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the presence of malicious code indicates potential for unauthorized access and data breaches.

More information can be found in the official GitHub repository of the esri package and through security advisories related to npm packages.

How To Fix

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

npm uninstall esri

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