Which versions of daswand102661 are malicious?

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

How do I remediate daswand102661 if I installed it?

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

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

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

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

Malicious package

daswand102661RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

daswand102661 is a confirmed malicious RubyGems package (MAL-2026-7609) 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 daswand102661 (RubyGems)

MAL-2026-7609

Immediate action

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

gem uninstall daswand102661

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

04e78d6fd548a8ed84e4cdeadc96688fb30d53c2b37b05c598ebed05ad452563

fed4eeef92a16cc96e057733aa40b5a178ce7b69b812028802b9ab31327732b2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for daswand102661 (version 0.0.1).
If you installed it — respond
Remove daswand102661 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 daswand102661 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. daswand102661 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-02260RLUA-2026-07964

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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