Which versions of lyatly-utils are malicious?

The following npm versions of lyatly-utils are flagged malicious: 99.0.0, 99.0.2, 99.0.3. Treat any of these as compromised.

How do I remediate lyatly-utils if I installed it?

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

If lyatly-utils 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 lyatly-utils part of a known attack campaign?

Yes — lyatly-utils is associated with the GHSA-q5j5-vc8g-m882, RLMA-2026-01424 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 lyatly-utils 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 lyatly-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lyatly-utils across your stack and pipelines.

Malicious package

lyatly-utilsnpm

Malicious code in lyatly-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-570

Immediate action

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

npm uninstall lyatly-utils

What this malware does

The package lyatly-utils was found to contain malicious code.

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

3 flagged

99.0.099.0.299.0.3

Indicators of compromise (SHA-256)

204e1babf8aef5194fc7046392fad75412787d49c6468fe0a18394f9bdc4e416

aa157e65bb67cd3f088cc4f38956e3f1b9cd202f73a212f4a92a87528eecf054

dbb32b78b726898f0914a59283be9576efd7f1a1381841f7bc0718c222d09513

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 lyatly-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lyatly-utils across your stack and pipelines.
If you installed it — respond
Remove lyatly-utils 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 lyatly-utils 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 lyatly-utils 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. lyatly-utils on npm has been identified as a malicious package (versions 99.0.0, 99.0.2, 99.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q5j5-vc8g-m882RLMA-2026-01424

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks lyatly-utils-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