Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

knot-devise-jwt-helperRubyGems

Malicious code in knot-devise-jwt-helper (RubyGems) Remove it immediately and rotate any exposed credentials.

MAL-2026-3632
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall knot-devise-jwt-helper

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
1.0.7

Indicators of compromise (SHA-256)

a4e4f74e90479d472a307d311d48214827e21cf93ecf9b0b62ff2cb72adb2c9e

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for knot-devise-jwt-helper (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging knot-devise-jwt-helper across your stack and pipelines.

  2. If you installed it — respond

    knot-devise-jwt-helper 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 knot-devise-jwt-helper was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks knot-devise-jwt-helper before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. knot-devise-jwt-helper on RubyGems has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

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

knot-devise-jwt-helper (RubyGems) malicious package — MAL-2026-3632 | O3 Security