Which versions of @joyfill/layouts are malicious?

The following npm versions of @joyfill/layouts are flagged malicious: 0.1.2-2773.beta.0. Treat any of these as compromised.

How do I remediate @joyfill/layouts if I installed it?

@joyfill/layouts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @joyfill/layouts — how do I know if it already compromised me?

If @joyfill/layouts 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 @joyfill/layouts part of a known attack campaign?

Yes — @joyfill/layouts is associated with the GHSA-887f-rwr9-wp54, IN-MAL-2026-013347 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 @joyfill/layouts 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 @joyfill/layouts (version 0.1.2-2773.beta.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @joyfill/layouts across your stack and pipelines.

Malicious package

@joyfill/layoutsnpm

@joyfill/layouts is a confirmed malicious npm package (MAL-2026-11161) that steals credentials and exfiltrates sensitive data (malicious version 0.1.2-2773.beta.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @joyfill/layouts (npm)

MAL-2026-11161

Immediate action

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

npm uninstall @joyfill/layouts

What this malware does

Analysis of @joyfill/[email protected] surfaced no a static rule matches and no traced code paths indicating exfiltration, install-time remote code execution, silent relay, credential distribution, backdoor, or self-propagation behavior. The package's shipped contents show no lifecycle-script droppers, no hardcoded attacker endpoints, no reads of installer secret paths, and no obfuscated payloads.

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

0.1.2-2773.beta.0

Indicators of compromise (SHA-256)

48d31efc1aa4ad0afbb16e357a08eb80ab4c39bca8dab1723ead698363e0edc2

b2f0675d4a2717361ec79b2c5a5cbf0ff0367e8d9cbf991f2f300df6c6b819ec

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @joyfill/layouts (version 0.1.2-2773.beta.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @joyfill/layouts across your stack and pipelines.
If you installed it — respond
@joyfill/layouts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @joyfill/layouts 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 @joyfill/layouts 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. @joyfill/layouts on npm has been identified as a malicious package (version 0.1.2-2773.beta.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-887f-rwr9-wp54IN-MAL-2026-013347

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @joyfill/layouts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database