What does the @modals/layout malware do?

The package @modals/layout was found to contain malicious code. The OpenSSF Package Analysis project identified '@modals/layout' @ 99999.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of @modals/layout are malicious?

The following npm versions of @modals/layout are flagged malicious: 99999.0.0, 99999.0.1. Treat any of these as compromised.

How do I remediate @modals/layout if I installed it?

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

If @modals/layout 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.

How do I find @modals/layout across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @modals/layout (2 malicious versions).

Malicious package

@modals/layoutnpm

Advisory published Mar 21, 2026Updated Mar 23, 2026

@modals/layout is a confirmed malicious npm package (MAL-2026-2019) that executes malicious code on install (malicious versions 99999.0.0, 99999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @modals/layout (npm)

MAL-2026-2019

Immediate action

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

npm uninstall @modals/layout

What this malware does

The package @modals/layout was found to contain malicious code.

The OpenSSF Package Analysis project identified '@modals/layout' @ 99999.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

99999.0.099999.0.1

Indicators of compromise (SHA-256)

423ea5070da3529e74e772e47cd0109f3dfc4a483645bfd0537e9007bd9ec60d

96441eae186edd4ea411d23ed37960f469e9609f6ab9af1b6fd0d2ca3143d6c7

2dd7a47296a1be165b33bf8cc140bf4b6b004025557cfb22a0b75c4ec8eea864

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @modals/layout (2 malicious versions).
If you installed it — respond
Remove @modals/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 @modals/layout 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. @modals/layout on npm has been identified as a malicious package (versions 99999.0.0, 99999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @modals/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