Which versions of sleek-pretty are malicious?

The following npm versions of sleek-pretty are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate sleek-pretty if I installed it?

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

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

Yes — sleek-pretty is associated with the GHSA-38w9-552m-96hh, RLMA-2026-05318, RLUA-2026-06491 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 sleek-pretty across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sleek-pretty (version 1.0.0).

Malicious package

sleek-prettynpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

sleek-pretty is a confirmed malicious npm package (MAL-2026-6878) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sleek-pretty (npm)

MAL-2026-6878

Immediate action

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

npm uninstall sleek-pretty

What this malware does

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

1.0.0

Indicators of compromise (SHA-256)

ba44435dd6e0686c11ff8a9e27c60eef2f2fbdbcdbd0c3936d1f07cc78d38090

944d8fef83a9b685ece304ddd483e7f4ce48c9d383e19bfdd4c5ecd68251e4a0

f2146e9f0aea49255bf09a24ba9e3f6814e8ab297dc075dbe43e0aacace93c4a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sleek-pretty (version 1.0.0).
If you installed it — respond
Remove sleek-pretty 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 sleek-pretty 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. sleek-pretty on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-38w9-552m-96hhRLMA-2026-05318RLUA-2026-06491

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sleek-pretty-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