Malicious Code Detected in frontend-config Package - MAL-2025-20969

frontend-config Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20969: Malicious code in frontend-config (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The frontend-config package is an npm library designed to assist developers in configuring front-end applications with ease. It provides a set of tools and configurations that streamline the development process. However, this package has been identified to contain malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the frontend-config package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall frontend-config

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 frontend-config package from your project until a secure version is released. You can do this by executing: npm uninstall frontend-config.

Conclusion

The frontend-config package has been identified as containing malicious code, which poses significant security risks. Users are advised to update or uninstall the package to protect their applications. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for frontend-config →

Share this vulnerability

FAQ

frontend-config is an npm package that helps developers configure front-end applications efficiently.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring your software remains secure.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall frontend-config

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