Which versions of frontastic are malicious?

The following npm versions of frontastic are flagged malicious: 90.9.0. Treat any of these as compromised.

How do I remediate frontastic if I installed it?

Remove frontastic from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed frontastic — how do I know if it already compromised me?

If frontastic was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is frontastic part of a known attack campaign?

Yes — frontastic is associated with the RLMA-2026-01330 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find frontastic across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for frontastic (version 90.9.0).

Malicious package

frontasticnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

frontastic is a confirmed malicious npm package (MAL-2026-1741) that executes malicious code on install (malicious version 90.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontastic (npm)

MAL-2026-1741

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall frontastic

What this malware does

The package frontastic was found to contain malicious code.

Malicious versions

1 flagged

90.9.0

Indicators of compromise (SHA-256)

97332806e1768b31d9dcbcbbb3238d2db97bdbf38360662227a589e3414a5482

e3a8ba3c5ef6ed185f82d46c61b62d6f2b4452c58a9c3705c117feac6806ceae

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for frontastic (version 90.9.0).
If you installed it — respond
Remove frontastic from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If frontastic was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. frontastic on npm has been identified as a malicious package (version 90.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01330

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks frontastic-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database