Which versions of vagrant_hvinfo are malicious?

The following RubyGems versions of vagrant_hvinfo are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate vagrant_hvinfo if I installed it?

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

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

Yes — vagrant_hvinfo is associated with the RLMA-2024-05848, RLUA-2024-10369, RLUA-2026-09676 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 vagrant_hvinfo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vagrant_hvinfo (version 0.1.3).

Malicious package

vagrant_hvinfoRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in vagrant_hvinfo (RubyGems)

MAL-2024-7044

Immediate action

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

gem uninstall vagrant_hvinfo

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

b0f30c109a259ba48d262e0c5ee06848fc2b5c601e5c9170f20f509362265de7

c076e43fbd237b829310d0006532ab6a11d267530e088afc2fe03e2fbd427dc7

7f68bc21b13c6c07b9c6440086e8af974aa8ea492a249991968097651f01d1be

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05848RLUA-2024-10369RLUA-2026-09676

References

Credits

ReversingLabs · finder

Detect & block this

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