Which versions of scaljanbfksf are malicious?

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

How do I remediate scaljanbfksf if I installed it?

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

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

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

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

Malicious package

scaljanbfksfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8585

Immediate action

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

gem uninstall scaljanbfksf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed51d500d9e44eb76a92645e3be188e5495f1099e0297d3c6f4914bbd2ed2bfd

850a3a95214ff77664ad491e641c0ecc564081b292f0373f106d2ea17588d9e3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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