NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

agentic-call-controlRubyGems

Advisory published Updated

agentic-call-control is a confirmed malicious RubyGems package (MAL-2026-18763) that steals credentials and exfiltrates sensitive data (malicious version 1.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in agentic-call-control (RubyGems)

MAL-2026-18763
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall agentic-call-control

What this malware does

The gem's native extension script executes during gem install and harvests installer-side data without consent. It collects host identifiers (current working directory, home directory, hostname, login name) and reads the contents of /etc/resolv.conf, /etc/passwd, and /etc/hosts, serializes them as JSON, and POSTs the payload over TLS to the hardcoded host k6rqb5d1inuytrro2u6arv87vy1vplda.oastify.com on port 443 using TCPSocket/OpenSSL. A DNS lookup to the same subdomain is also issued as an out-of-band beacon. The destination is a Burp Collaborator subdomain — attacker-controlled out-of-band interaction infrastructure unrelated to any declared publisher or build dependency. There is no native source tree or build logic that would require this network activity; the extension script's sole effect on install is reconnaissance exfiltration.

Malicious versions

1 flagged
1.1.8

Indicators of compromise (SHA-256)

6604e2b2afca5be9f394786598898c0d718100ef3cb3595590fb74949b3eb9b5

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for agentic-call-control (version 1.1.8).

  2. If you installed it — respond

    agentic-call-control is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If agentic-call-control 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. agentic-call-control on RubyGems has been identified as a malicious package (version 1.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022569

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks agentic-call-control-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

agentic-call-control (RubyGems) malicious package — MAL-2026-18763 | O3 Security