Which versions of secrequeryabc are malicious?

The following RubyGems versions of secrequeryabc are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate secrequeryabc if I installed it?

Remove secrequeryabc 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.

I already installed secrequeryabc — how do I know if it already compromised me?

If secrequeryabc 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 secrequeryabc part of a known attack campaign?

Yes — secrequeryabc is associated with the RLMA-2026-03238, RLUA-2026-09133 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 secrequeryabc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for secrequeryabc (version 0.0.1).

Malicious package

secrequeryabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

secrequeryabc is a confirmed malicious RubyGems package (MAL-2026-8587) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in secrequeryabc (RubyGems)

MAL-2026-8587

Immediate action

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

gem uninstall secrequeryabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ec76452d484353a02b45473171419edebd20f6836fdaf1de3f760e02fbc8520

38eb00b90b6b8a8cf76606f0c82860bc343704b1ff8f9ea49bcaf415c054e890

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03238RLUA-2026-09133

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks secrequeryabc-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database