Malicious Code Detected in bric-gis Package - Security Alert

bric-gis Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16162: Malicious code in bric-gis (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 bric-gis package is an npm library designed for geographic information system (GIS) applications. It provides functionalities for mapping and spatial data manipulation. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the bric-gis package originates from the inclusion of malicious code that can compromise the integrity of applications using this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. It is crucial for developers to understand the implications of using this package and the potential risks associated with it.

How To Fix

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

npm uninstall bric-gis

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 avoid using the bric-gis package altogether and explore alternative libraries that provide similar GIS functionalities without the associated risks.

Conclusion

The bric-gis package has been flagged for containing malicious code, which poses serious security risks to applications. It is essential for developers to take immediate action by removing the package and considering secure alternatives. Regular monitoring of dependencies is vital to maintain application security.

See every vulnerability recorded for bric-gis →

Share this vulnerability

FAQ

The bric-gis package is an npm library used for geographic information system applications, providing mapping and spatial data manipulation functionalities.

The specific nature of the malicious code has not been disclosed, but it poses risks such as unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, it can help identify if your application is at risk.

The best mitigation strategy is to remove the bric-gis package and replace it with a secure alternative. Regularly updating your dependencies is also crucial.

You can visit Vulert's playground at Vulert Scanner to check if your application is affected by known vulnerabilities without requiring a signup.

How To Fix

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

npm uninstall bric-gis

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