Which versions of gimme-vins are malicious?

The following RubyGems versions of gimme-vins are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate gimme-vins if I installed it?

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

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

Yes — gimme-vins is associated with the RLMA-2024-05738, RLUA-2024-10257, RLUA-2026-08149 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 gimme-vins across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gimme-vins (version 0.0.3).

Malicious package

gimme-vinsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

gimme-vins is a confirmed malicious RubyGems package (MAL-2024-6932) that executes malicious code on install (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gimme-vins (RubyGems)

MAL-2024-6932

Immediate action

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

gem uninstall gimme-vins

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

18ca0a42215f6c07362a6f905631d92629d1e1f51e386597d4015b0a4acf8eb6

fa0861227a00922a02ccc15cf0b4405329a14f4e9e2d67fb45b78443a524e7bc

c8c705fa265973dd7a50cdbc528c8a353c2bbfefeb3c576b09236e5a7015fc53

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05738RLUA-2024-10257RLUA-2026-08149

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks gimme-vins-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