Which versions of lamfoss28330 are malicious?

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

How do I remediate lamfoss28330 if I installed it?

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

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

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

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

Malicious package

lamfoss28330RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7861

Immediate action

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

gem uninstall lamfoss28330

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6638afda12d9aaecf7519c322293f4ce7efc6284ac68f1ef57f9234747d08d2e

2389c881097064e22125b393783add3d32ae494d5a43e8e0d06870e30f91d0c5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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