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

monolith-twirp-snippy-snippyRubyGems

Malicious code in monolith-twirp-snippy-snippy (RubyGems) Remove it immediately and rotate any exposed credentials.

MAL-2025-46917
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall monolith-twirp-snippy-snippy

What this malware does

The OpenSSF Package Analysis project identified 'monolith-twirp-snippy-snippy' @ 1.0.4 (rubygems) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.4

Indicators of compromise (SHA-256)

48e4b752eb90b82df41239d8194646b9ab47b4e9e147dae4011c665a05d776b0

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove monolith-twirp-snippy-snippy 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.

  3. Did it already run?

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

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks monolith-twirp-snippy-snippy-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.

monolith-twirp-snippy-snippy (RubyGems) malicious package — MAL-2025-46917 | O3 Security