Critical Malicious Code Vulnerability in @cbre-internal/mapping-component Package

Summary

14/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5850: Malicious code in @cbre-internal/mapping-component (npm). Affects @cbre-internal/mapping-component versions 99.9.0. 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 @cbre-internal/mapping-component is an npm package designed for mapping functionalities within applications. It is utilized by developers to integrate mapping features seamlessly. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @cbre-internal/mapping-component package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, secrets, and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall @cbre-internal/mapping-component

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 measure, you can isolate the affected application from the network to prevent further exploitation while you work on removing the package. Additionally, rotate all secrets and keys stored on the compromised system immediately from a secure environment.

Conclusion

The @cbre-internal/mapping-component package contains malicious code that poses a significant threat to any system using it. Immediate action is required to remove the package and secure sensitive information. Regular monitoring and updates are essential to maintain security.

See every vulnerability recorded for @cbre-internal/mapping-component →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any sensitive information stored on the affected system.

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.

Yes, you can isolate the affected application from the network and rotate any stored secrets and keys.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, data breaches, and loss of control over your systems.

While removing the package is essential, there is no guarantee that all malicious software has been eliminated. A thorough security audit is recommended.

How To Fix

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

npm uninstall @cbre-internal/mapping-component

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