Which versions of dasswcal71 are malicious?

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

How do I remediate dasswcal71 if I installed it?

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

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

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

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

Malicious package

dasswcal71RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7608

Immediate action

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

gem uninstall dasswcal71

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

93bf6a8956462ba10666a0ce6795b38269ef49ddeb7405f78586cf89bac4085f

1a4f1d14dc8767f201ca18dfddc568d416330566401e340e8eaaba2f9c2a0131

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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