Which versions of chalk-standard are malicious?

The following npm versions of chalk-standard are flagged malicious: 5.6.2. Treat any of these as compromised.

How do I remediate chalk-standard if I installed it?

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

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

Yes — chalk-standard is associated with the RLMA-2026-05019, RLUA-2026-06151 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 chalk-standard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chalk-standard (version 5.6.2).

Malicious package

chalk-standardnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

chalk-standard is a confirmed malicious npm package (MAL-2026-7245) that executes malicious code on install (malicious version 5.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chalk-standard (npm)

MAL-2026-7245

Immediate action

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

npm uninstall chalk-standard

Malicious versions

1 flagged

5.6.2

Indicators of compromise (SHA-256)

afea243518ef7a54935e0307783ba9857ca8eed138b8ba9ab60e1d0a44f5ea18

1d8cba70430acfd3fd4c955178f119155615d1dca0c697d9e4f0788e989dda84

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05019RLUA-2026-06151

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks chalk-standard-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