Which versions of notification-settings-layout are malicious?

The following npm versions of notification-settings-layout are flagged malicious: 99.0.0, 99.0.1, 99.0.2. Treat any of these as compromised.

How do I remediate notification-settings-layout if I installed it?

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

If notification-settings-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.

Is notification-settings-layout part of a known attack campaign?

Yes — notification-settings-layout is associated with the RLMA-2026-01464 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 notification-settings-layout across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for notification-settings-layout (3 malicious versions).

Malicious package

notification-settings-layoutnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

notification-settings-layout is a confirmed malicious npm package (MAL-2026-1805) that executes malicious code on install (malicious versions 99.0.0, 99.0.1, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in notification-settings-layout (npm)

MAL-2026-1805

Immediate action

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

npm uninstall notification-settings-layout

What this malware does

The package notification-settings-layout was found to contain malicious code.

Malicious versions

3 flagged

99.0.099.0.199.0.2

Indicators of compromise (SHA-256)

20d4f5e76814b4456b6656f2954207aebdaaf3cad0295ed604db7ef27220bce4

77ec9a9823eefe0c031995eea2a7f2fc660ebf4843a6aaf365c042a8dbab2cb7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01464

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks notification-settings-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