Which versions of chalk-thrift are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chalk-thrift (version 0.1.17).

Malicious package

chalk-thriftRubyGems

Advisory published Dec 23, 2025Updated Jul 23, 2026

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

Malicious code in chalk-thrift (RubyGems)

MAL-2025-192903

Immediate action

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

gem uninstall chalk-thrift

Malicious versions

1 flagged

0.1.17

Indicators of compromise (SHA-256)

760415061aa3d189b26288e7fbc7a676b118024ef089870b2970b761e8dca425

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06610

Credits

ReversingLabs · finder

Detect & block this

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