Which versions of knot-activesupport-logger are malicious?

The following RubyGems versions of knot-activesupport-logger are flagged malicious: 7.1.6. Treat any of these as compromised.

How do I remediate knot-activesupport-logger if I installed it?

knot-activesupport-logger 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.

I already installed knot-activesupport-logger — how do I know if it already compromised me?

If knot-activesupport-logger 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.

How do I find knot-activesupport-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for knot-activesupport-logger (version 7.1.6).

Malicious package

knot-activesupport-loggerRubyGems

Advisory published May 13, 2026Updated Jul 23, 2026

knot-activesupport-logger is a confirmed malicious RubyGems package (MAL-2026-3630) that steals credentials and exfiltrates sensitive data (malicious version 7.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in knot-activesupport-logger (RubyGems)

MAL-2026-3630

Immediate action

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

gem uninstall knot-activesupport-logger

What this malware does

This package is a malicious packages part of the Go BufferZoneCorp and RubyGems knot-theory clusters. The packages in this cluster steal credentials, set up ssh access and tamper with build/workflow environmetn variables.

Malicious versions

1 flagged

7.1.6

Indicators of compromise (SHA-256)

a4e4f74e90479d472a307d311d48214827e21cf93ecf9b0b62ff2cb72adb2c9e

Detection & response playbook

Credential / info stealer

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

References

socket.dev

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database