Malicious Code Detected in @fmr-ap149494/apex-base-component: Version 99.9.1
Summary
MAL-2026-17929: Malicious code in @fmr-ap149494/apex-base-component (npm). Affects @fmr-ap149494/apex-base-component versions 99.9.1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package @fmr-ap149494/apex-base-component is an npm library designed for building Apex components. It is utilized in various applications for its functionality and ease of integration. However, version 99.9.1 has been flagged for containing malicious code that compromises security.
Vulnerability Detail
The vulnerability in @fmr-ap149494/apex-base-component arises from its communication with a domain associated with malicious activities. This could lead to unauthorized data access, potential data breaches, or exploitation of the affected systems. The origin of this vulnerability is linked to the package's interaction with external malicious domains, which can be exploited by attackers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @fmr-ap149494/apex-base-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 workaround, you can remove the package from your project until a secure version is released. You can do this by running: npm uninstall @fmr-ap149494/apex-base-component.
Conclusion
The @fmr-ap149494/apex-base-component package version 99.9.1 has been identified as malicious due to its communication with harmful domains. It is crucial to update or remove the package to safeguard your application from potential threats.
See every vulnerability recorded for @fmr-ap149494/apex-base-component →
FAQ
The package communicates with a domain known for malicious activities, which poses a risk of data breaches and unauthorized access.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Yes, it is advisable to update to the latest version of the package, which may contain security patches.
Consider removing the package from your project as a temporary measure until a secure version is available.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your software remains secure.