Which versions of daslam173851 are malicious?

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

How do I remediate daslam173851 if I installed it?

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

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

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

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

Malicious package

daslam173851RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7605

Immediate action

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

gem uninstall daslam173851

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0ccd651ee684b6e509e468825893640d03cc4fcb1a3a48a25efdbaecb1866d03

f773e1e35d0e070840650148c938c8e0ba4d65a9d75085969877c857795f6251

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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