Which versions of nhtsa-vin are malicious?

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

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

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

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

Yes — nhtsa-vin is associated with the RLMA-2024-05802, RLUA-2024-10323, RLUA-2026-08653 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 nhtsa-vin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nhtsa-vin (version 0.0.8).

Malicious package

nhtsa-vinRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in nhtsa-vin (RubyGems)

MAL-2024-6996

Immediate action

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

gem uninstall nhtsa-vin

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

66af91436918240d5f206a4b9916d114cf097b5b9bc66609ad3790486d247144

3f39dbc647af732fc5a86d8bcbdb48a449c6d96f4b3ffdd6359f65c1edbb6adb

22d8c64bf81b555b0818a168490ace9a947e0cd974465dc5d6ba43407503a049

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05802RLUA-2024-10323RLUA-2026-08653

References

Credits

ReversingLabs · finder

Detect & block this

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