Which versions of maventa_utils are malicious?

The following RubyGems versions of maventa_utils are flagged malicious: 3.0.0, 4.0.0. Treat any of these as compromised.

How do I remediate maventa_utils if I installed it?

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

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

Yes — maventa_utils is associated with the RLMA-2025-03727, RLUA-2025-06619 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 maventa_utils across my projects, lockfiles, and CI pipelines?

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

Malicious package

maventa_utilsRubyGems

Advisory published Jul 31, 2025Updated Jul 23, 2026

maventa_utils is a confirmed malicious RubyGems package (MAL-2025-6628) that executes malicious code on install (malicious versions 3.0.0, 4.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in maventa_utils (RubyGems)

MAL-2025-6628

Immediate action

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

gem uninstall maventa_utils

Malicious versions

2 flagged

3.0.04.0.0

Indicators of compromise (SHA-256)

70cb07dc672a7fc6b60c63c3817f8dbb76175446870112407bcb88c801f98323

c8b9b3b0fc24900de7648a34850842ec11cc766a4a26177e055246c62944bcdc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-03727RLUA-2025-06619

References

intel.aikido.dev

Credits

ReversingLabs · finder

Detect & block this

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