Which versions of brida-frida-hooks are malicious?

The following RubyGems versions of brida-frida-hooks are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate brida-frida-hooks if I installed it?

brida-frida-hooks 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 brida-frida-hooks — how do I know if it already compromised me?

If brida-frida-hooks 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.

Is brida-frida-hooks part of a known attack campaign?

Yes — brida-frida-hooks is associated with the IN-MAL-2026-022532 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find brida-frida-hooks across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for brida-frida-hooks (version 1.0.1).

Malicious package

brida-frida-hooksRubyGems

Advisory published Nov 4, 2026Updated Nov 4, 2026

brida-frida-hooks is a confirmed malicious RubyGems package (MAL-2026-18598) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in brida-frida-hooks (RubyGems)

MAL-2026-18598

Immediate action

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

gem uninstall brida-frida-hooks

What this malware does

The gem declares an extension script in its gemspec that executes during gem install. On install, the script collects installer identity and local system data — current working directory, home directory, hostname, username, and the contents of /etc/resolv.conf, /etc/passwd, and /etc/hosts — and POSTs them over TLS via a raw TCPSocket to the hardcoded Burp Collaborator subdomain bjyhowqsve7p6i4fflj14mly8pel2bq0.oastify.com on port 443. The exfiltration is unrelated to the gem's stated 'simple demo' purpose and runs automatically on default install.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

cc383ba7728e9aec64324ce8b1c9b354b0331d7c404888e39d1d127885381e1d

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-022532

References

rubygems.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks brida-frida-hooks-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