Which versions of swpdf1311191 are malicious?

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

How do I remediate swpdf1311191 if I installed it?

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

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

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

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

Malicious package

swpdf1311191RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8957

Immediate action

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

gem uninstall swpdf1311191

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0a5b5a3fe91001b9bdf73210554a35f9e2771498cbee1a915de131cee7fe8a17

6c60428834b31d43316d1f94d42c275bb5ab572ed01c86b2b8a7bd97ab48434d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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