Which versions of daswandcal71 are malicious?

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

How do I remediate daswandcal71 if I installed it?

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

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

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

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

Malicious package

daswandcal71RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7610

Immediate action

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

gem uninstall daswandcal71

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

36c3cb42ce806cd56b9b2e791689877fcd8e15ff7a78158efe8009ab49ab4083

e575d285abad28daf918817f6cf763bf5cef050ee63ca1bbd0f028e1fc43732b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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