Malicious Code Detected in geobase6 Package - Security Alert

geobase6 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21333: Malicious code in geobase6 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The geobase6 package is an npm library designed for geolocation services, providing users with functionalities to access geographical data. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.

Vulnerability Detail

The vulnerability in the geobase6 package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially allow attackers to execute harmful actions, such as data theft or unauthorized access to sensitive information. The issue is present in all versions starting from 0, making it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall geobase6

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

Conclusion

The discovery of malicious code in the geobase6 package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for geobase6 →

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions, potentially leading to data breaches or system compromise.

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

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

Consider removing the geobase6 package from your project as a temporary measure until a secure version is released.

Utilize tools like Vulert, which can help you monitor your project's dependencies for vulnerabilities in real-time.

How To Fix

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

npm uninstall geobase6

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