Which versions of scaljan2momxm are malicious?

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

How do I remediate scaljan2momxm if I installed it?

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

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

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

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

Malicious package

scaljan2momxmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8584

Immediate action

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

gem uninstall scaljan2momxm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bec095459bbfd66dc6007548b41bb1f455a9287b113aa7f2f880e7b90c78ee83

c6bc87aaaea1ee0493763f0b26abe6d5c128c858ea672b8ff1180c9719566747

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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