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

proto-registry-metadata-apiRubyGems

Malicious code in proto-registry-metadata-api (RubyGems) Remove it immediately and rotate any exposed credentials.

MAL-2025-46920
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
gem uninstall proto-registry-metadata-api

What this malware does

The OpenSSF Package Analysis project identified 'proto-registry-metadata-api' @ 1.11.3.87.g981ef7d3d (rubygems) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
1.11.3.87.g981ef7d3d

Indicators of compromise (SHA-256)

f1f7ab6f94cef6b0a1e53365370e91527c5c546ab409345d8a77877f5927f677

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 proto-registry-metadata-api (version 1.11.3.87.g981ef7d3d). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging proto-registry-metadata-api across your stack and pipelines.

  2. If you installed it — respond

    Remove proto-registry-metadata-api 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 proto-registry-metadata-api 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 proto-registry-metadata-api 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. proto-registry-metadata-api on RubyGems has been identified as a malicious package (version 1.11.3.87.g981ef7d3d 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 proto-registry-metadata-api-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.

proto-registry-metadata-api (RubyGems) malicious package — MAL-2025-46920 | O3 Security