Which versions of swpdf1311181 are malicious?

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

How do I remediate swpdf1311181 if I installed it?

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

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

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

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

Malicious package

swpdf1311181RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8956

Immediate action

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

gem uninstall swpdf1311181

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

73355064962b7cd4385ca2309cfe590196c0ee60775a223abcdddba6996619f5

d9a27274333b898fb43afa3e508133e101fbcf8e8f819d1305f42f30f453a356

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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