Which versions of control-character-command-injection are malicious?

The following RubyGems versions of control-character-command-injection are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate control-character-command-injection if I installed it?

Remove control-character-command-injection 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 control-character-command-injection — how do I know if it already compromised me?

If control-character-command-injection 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 control-character-command-injection part of a known attack campaign?

Yes — control-character-command-injection is associated with the IN-MAL-2026-022570 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 control-character-command-injection across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for control-character-command-injection (version 1.0.1).

Malicious package

control-character-command-injectionRubyGems

Advisory published Nov 8, 2026Updated Nov 8, 2026

control-character-command-injection is a confirmed malicious RubyGems package (MAL-2026-18764) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in control-character-command-injection (RubyGems)

MAL-2026-18764

Immediate action

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

gem uninstall control-character-command-injection

What this malware does

The gem declares an extension script in metadata.yaml that RubyGems executes during gem install. At install time the script reads host identifiers (hostname, username, current working directory, home directory) and the contents of /etc/resolv.conf, /etc/passwd, and /etc/hosts, then opens a TLS connection via TCPSocket to the Burp Collaborator subdomain xuv3zi1e60ibh4f1q7unf8wkjbpad01p.oastify.com on port 443 and POSTs the collected data as a JSON body. A DNS lookup to the same host is also performed. The destination is an out-of-band interaction host unrelated to any legitimate publisher infrastructure, and the behavior fires automatically on install without user interaction.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

83327b9e45cb49b02f4a3681837f5acdc84f15373a85648f4409946e6fa72f75

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-022570

References

rubygems.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks control-character-command-injection-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