Which versions of twitter-cards are malicious?

The following RubyGems versions of twitter-cards are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate twitter-cards if I installed it?

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

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

Yes — twitter-cards is associated with the RLMA-2024-05845, RLUA-2024-10366, RLUA-2026-09610 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-cards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for twitter-cards (version 0.1.0).

Malicious package

twitter-cardsRubyGems

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

Malicious code in twitter-cards (RubyGems)

MAL-2024-7041

Immediate action

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

gem uninstall twitter-cards

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

d80653233aefa9aa9218794899359bb79d4502740e04dc904cbc479557e117b2

1869d26ab46bdb982f6905d426c75bfaf783cf5521726252275b37fd6ef400af

157c331eb0d25324f8cfc6c4b1331c02004c2dbf9779e21e491c02830d2feb26

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05845RLUA-2024-10366RLUA-2026-09610

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks twitter-cards-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