Which versions of chalk-hostname are malicious?

The following RubyGems versions of chalk-hostname are flagged malicious: 0.0.25. Treat any of these as compromised.

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

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

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

Yes — chalk-hostname is associated with the RLMA-2025-06606 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-hostname across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chalk-hostname (version 0.0.25).

Malicious package

chalk-hostnameRubyGems

Advisory published Dec 23, 2025Updated Jul 23, 2026

chalk-hostname is a confirmed malicious RubyGems package (MAL-2025-192899) that executes malicious code on install (malicious version 0.0.25). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chalk-hostname (RubyGems)

MAL-2025-192899

Immediate action

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

gem uninstall chalk-hostname

Malicious versions

1 flagged

0.0.25

Indicators of compromise (SHA-256)

dc1e691b373fdd5f74f4bdf0bbb3559fdc710010365a904e04660807e36faffd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06606

Credits

ReversingLabs · finder

Detect & block this

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