What does the myads-layout malware do?

The package myads-layout was found to contain malicious code. The OpenSSF Package Analysis project identified 'myads-layout' @ 6.5.5 (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 myads-layout are malicious?

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

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

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

If myads-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 myads-layout across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for myads-layout (version 6.5.5).

Malicious package

myads-layoutnpm

Advisory published Feb 10, 2026Updated Feb 23, 2026

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

Malicious code in myads-layout (npm)

MAL-2026-836

Immediate action

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

npm uninstall myads-layout

What this malware does

The package myads-layout was found to contain malicious code.

The OpenSSF Package Analysis project identified 'myads-layout' @ 6.5.5 (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

1 flagged

6.5.5

Indicators of compromise (SHA-256)

daaebe7963626ff1bbd9c1182c246f9c508f6f3b7add576234dc5b4651276b24

8d196800be4de842ce4eb526181a86b7d78e5e3851954256a68d9cda3dab4a89

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for myads-layout (version 6.5.5).
If you installed it — respond
Remove myads-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 myads-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. myads-layout on npm has been identified as a malicious package (version 6.5.5 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 myads-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