Which versions of edmunds-vin are malicious?

The following RubyGems versions of edmunds-vin are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate edmunds-vin if I installed it?

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

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

Yes — edmunds-vin is associated with the RLMA-2024-05689, RLUA-2024-10208, RLUA-2026-08032 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 edmunds-vin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for edmunds-vin (version 0.1.1).

Malicious package

edmunds-vinRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

edmunds-vin is a confirmed malicious RubyGems package (MAL-2024-6883) that executes malicious code on install (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in edmunds-vin (RubyGems)

MAL-2024-6883

Immediate action

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

gem uninstall edmunds-vin

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

0cab74f50ccba9525014984c1fdf6898fb753903c08f2230614704e270968a7d

4bef2a497fe007af1552e8458a02b8dfda90a4cf522276fec918e9b4d7d000c0

91a6542585b6fe49944a377ab5d2589ab5eb1b76e3a2cc463546dc694b56cc44

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05689RLUA-2024-10208RLUA-2026-08032

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks edmunds-vin-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