Which versions of zbt_element_definer are malicious?

The following RubyGems versions of zbt_element_definer are flagged malicious: 1.0.0, 1.0.8. Treat any of these as compromised.

How do I remediate zbt_element_definer if I installed it?

Remove zbt_element_definer 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 zbt_element_definer — how do I know if it already compromised me?

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

Yes — zbt_element_definer is associated with the RLMA-2024-10373, RLUA-2024-11216, RLUA-2026-10148 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 zbt_element_definer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zbt_element_definer (2 malicious versions).

Malicious package

zbt_element_definerRubyGems

Advisory published Oct 16, 2024Updated Sep 24, 2026

zbt_element_definer is a confirmed malicious RubyGems package (MAL-2024-10222) that executes malicious code on install (malicious versions 1.0.0, 1.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zbt_element_definer (RubyGems)

MAL-2024-10222

Immediate action

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

gem uninstall zbt_element_definer

Malicious versions

2 flagged

1.0.01.0.8

Indicators of compromise (SHA-256)

cdc59113bb9f05ce73ed36f6affaca9eeeb16764a9e26266f1a88d1d188d57bd

f004864111461897845a2cf4aadbe669701bbad9242cd52884dda02d03b788c9

26cb7527b421fa1b7efc6e693bb90f2db72688e4d95d22b54d39f0ef442f1b9b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-10373RLUA-2024-11216RLUA-2026-10148

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zbt_element_definer-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