Which versions of aiwvntrvdltc are malicious?

The following RubyGems versions of aiwvntrvdltc are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate aiwvntrvdltc if I installed it?

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

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

Yes — aiwvntrvdltc is associated with the RLMA-2026-02183 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 aiwvntrvdltc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aiwvntrvdltc (version 0.0.1).

Malicious package

aiwvntrvdltcRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

aiwvntrvdltc is a confirmed malicious RubyGems package (MAL-2026-7532) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiwvntrvdltc (RubyGems)

MAL-2026-7532

Immediate action

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

gem uninstall aiwvntrvdltc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

244bbcd6f23326f5a5a58a1cedae4de00f6054f47c65eda567b98d5580c84872

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02183

Credits

ReversingLabs · finder

Detect & block this

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