Which versions of twitter_vine are malicious?

The following RubyGems versions of twitter_vine are flagged malicious: 0.1.9. Treat any of these as compromised.

How do I remediate twitter_vine if I installed it?

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

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

Yes — twitter_vine is associated with the RLMA-2024-05846, RLUA-2024-10367, RLUA-2026-09611 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 twitter_vine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for twitter_vine (version 0.1.9).

Malicious package

twitter_vineRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in twitter_vine (RubyGems)

MAL-2024-7042

Immediate action

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

gem uninstall twitter_vine

Malicious versions

1 flagged

0.1.9

Indicators of compromise (SHA-256)

f4928b51e9e2189aec8c572250998cfd74b972a112ae4d69d38ab63980a1a52e

89709ace33df251e79f2af959afa6ab675156f9cbc1e314fcc7b199a3addb14e

650af18f01ca140cfeb62f30db4b6f2ce91f9c71873b34b54f74160a8819d711

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05846RLUA-2024-10367RLUA-2026-09611

References

Credits

ReversingLabs · finder

Detect & block this

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