Malicious Code Vulnerability in frontastic Package

frontastic Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1741: Malicious code in frontastic (npm). Affects frontastic versions 90.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The frontastic package is a JavaScript library used in web development, particularly for building modern e-commerce applications. It provides a range of functionalities including user interface components, API integrations, and performance optimizations. However, recent findings have revealed that this package is susceptible to malicious code injection, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability identified in the frontastic package stems from malicious code embedded within version 90.9.0. This code can potentially compromise the security of applications by allowing unauthorized access to sensitive data or executing harmful commands. The origin of this vulnerability has been traced back to a malicious actor who manipulated the package, making it imperative for users to remain vigilant and update their dependencies regularly.

How To Fix

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

npm uninstall frontastic

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, users can avoid using the affected version (90.9.0) of the frontastic package until a secure version is confirmed. It is advisable to check the package-lock.json file for any dependencies that may still reference the vulnerable version and update them accordingly.

Conclusion

The discovery of malicious code within the frontastic package highlights the importance of maintaining updated dependencies in software development. By following the recommended steps to update the package and utilizing tools like Vulert for real-time monitoring, developers can safeguard their applications against potential threats.

See every vulnerability recorded for frontastic →

Share this vulnerability

FAQ

Frontastic is a JavaScript library designed for building modern web applications, particularly in the e-commerce sector.

The malicious code can lead to unauthorized access to sensitive data and may execute harmful commands, compromising the security of your application.

You can use the Vulert 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, refrain from using the affected version and monitor for updates from the package maintainers.

Detailed information about this vulnerability can be found on the GitHub repository of the malicious packages.

How To Fix

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

npm uninstall frontastic

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