Malicious Code Detected in frontend-release-manager Package

frontend-release-manager Updated 02 Oct 2025

Summary

09/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5693: Malicious code in frontend-release-manager (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The frontend-release-manager is an npm package designed to facilitate the management of frontend releases in web applications. It allows developers to streamline their deployment processes and manage version control effectively. However, this package has been found to contain embedded malicious code, posing significant security risks to any system that utilizes it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the frontend-release-manager package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full system compromise, data breaches, and potential exploitation by malicious actors. The specific technical aspects involve the package being flagged for containing code that appears to be malicious in nature, as identified by the Open Source Vulnerability database.

How To Fix

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

npm uninstall frontend-release-manager

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 frontend-release-manager package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that all secrets and keys stored on the affected computer are rotated immediately from a secure system.

Conclusion

The frontend-release-manager package has been identified as containing malicious code, which poses a significant security threat to systems that utilize it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor for updates and consider alternative solutions.

See every vulnerability recorded for frontend-release-manager →

Share this vulnerability

FAQ

You should remove the package immediately and rotate any secrets or keys stored on the affected system.

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

Currently, there is no patched version available. It is recommended to remove the package until a safe version is released.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation by attackers.

It is highly discouraged to continue using the package, as it may still pose risks even if you believe you do not store sensitive information.

How To Fix

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

npm uninstall frontend-release-manager

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