Which versions of frontend-layout are malicious?

The following npm versions of frontend-layout are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate frontend-layout if I installed it?

Remove frontend-layout 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 frontend-layout — how do I know if it already compromised me?

If frontend-layout was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is frontend-layout part of a known attack campaign?

Yes — frontend-layout is associated with the GHSA-w45m-xcxq-j9vp, RLMA-2025-05373, RLUA-2025-05799 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 frontend-layout across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for frontend-layout (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-layout across your stack and pipelines.

Malicious package

frontend-layoutnpm

frontend-layout is a confirmed malicious npm package (MAL-2025-48279) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontend-layout (npm)

MAL-2025-48279

Immediate action

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

npm uninstall frontend-layout

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

dd81764709c7d0f5174dd0a979519b3c85894302b3df75acedbf1de8500d3c07

6c79c0302b2ba1555b1967edddf992ec2dffdd55bc7d5c87da5ab6f2b5a73848

fc1f4e1e1c3d611cd3a6f49ef8ec3442c62dd879d129cff8622d0eb690f55f45

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for frontend-layout (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-layout across your stack and pipelines.
If you installed it — respond
Remove frontend-layout 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 frontend-layout was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks frontend-layout before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-w45m-xcxq-j9vpRLMA-2025-05373RLUA-2025-05799

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks frontend-layout-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