Critical Malicious Code Vulnerability in frontend-js-state-web Package

frontend-js-state-web Updated 03 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-680: Malicious code in frontend-js-state-web (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-js-state-web package is a JavaScript library used in web development to manage application state in a frontend environment. It is commonly utilized in various web applications for its ability to streamline state management and improve performance. However, this package has been identified as containing malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the frontend-js-state-web package. This code can compromise the entire system, allowing unauthorized access to sensitive data, including secrets and keys stored on the affected machine. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over the system. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall frontend-js-state-web

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

Currently, there are no effective workarounds to mitigate the risks associated with this malicious package. The only recommended action is to uninstall the package and secure the system.

Conclusion

The frontend-js-state-web package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for frontend-js-state-web →

Share this vulnerability

FAQ

The malicious code is designed to compromise the security of the system, potentially allowing unauthorized access to sensitive information.

If you have the frontend-js-state-web package installed, your system is considered compromised. It is advisable to remove the package immediately.

After uninstalling the package, rotate all secrets and keys stored on the affected system from a secure computer to prevent unauthorized access.

No, there is currently no patched version of the frontend-js-state-web package available.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check for vulnerabilities in your application using the Vulert playground without any signup.

How To Fix

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

npm uninstall frontend-js-state-web

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