Malicious Code Detected in earth-grid-bad-visualize-warn Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19084: Malicious code in earth-grid-bad-visualize-warn (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The earth-grid-bad-visualize-warn package is an npm library designed for visualizing geographical data using grid-based methods. It is intended for developers looking to enhance their applications with geographical visualizations. However, this package has been found to contain malicious code that could compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the earth-grid-bad-visualize-warn package stems from the inclusion of malicious code that can execute harmful operations on the user's system. This code could lead to unauthorized access, data breaches, or system corruption. 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 earth-grid-bad-visualize-warn

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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and community feedback before integrating it into your project.

Conclusion

The discovery of malicious code in the earth-grid-bad-visualize-warn package poses a significant threat to users. It is crucial to take immediate action by uninstalling the package and exploring alternative solutions. Regular monitoring for updates and vulnerabilities is essential to maintain application security.

See every vulnerability recorded for earth-grid-bad-visualize-warn →

Share this vulnerability

FAQ

It is an npm package designed for visualizing geographical data using grid methods.

The package contains code that can execute harmful operations, potentially leading to unauthorized access or data breaches.

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.

You should uninstall the package immediately and consider using alternative libraries for geographical visualizations.

Currently, there is no patched version available. Users are advised to uninstall the package until a secure version is released.

How To Fix

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

npm uninstall earth-grid-bad-visualize-warn

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