Which versions of devino-sms are malicious?

The following RubyGems versions of devino-sms are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate devino-sms if I installed it?

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

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

Yes — devino-sms is associated with the RLMA-2024-05668, RLUA-2024-10187, RLUA-2026-07975 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 devino-sms across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for devino-sms (version 0.0.2).

Malicious package

devino-smsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in devino-sms (RubyGems)

MAL-2024-6862

Immediate action

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

gem uninstall devino-sms

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

a54a4c28ff420321ad052ef56b79e8508c19fe8b30b8ea0a48db3f30a5e2a757

1c7aff8e0912cb5f7009a2cc45bf4c9049b84a617a826270acb155edbacc9d3c

aa514d7c77001e948ef8b317956c97ffec5d460352241469bcf8ec648f741b5e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05668RLUA-2024-10187RLUA-2026-07975

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks devino-sms-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