Which versions of pathpkg94321yy are malicious?

The following RubyGems versions of pathpkg94321yy are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate pathpkg94321yy if I installed it?

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

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

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

Search your lockfiles and build artifacts for pathpkg94321yy (2 malicious versions).

Malicious package

pathpkg94321yyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

pathpkg94321yy is a confirmed malicious RubyGems package (MAL-2026-8411) that executes malicious code on install (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pathpkg94321yy (RubyGems)

MAL-2026-8411

Immediate action

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

gem uninstall pathpkg94321yy

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

0b070560a5397b97cdadd20a7e00f6690eaef70d32d8e8c4387ad2626c293b21

c93858c13b1258490500403bd36ba31221262a1dd1950eab35b3ea288abd7a77

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pathpkg94321yy (2 malicious versions).
If you installed it — respond
Remove pathpkg94321yy 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 pathpkg94321yy 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. pathpkg94321yy on RubyGems has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03062RLUA-2026-08932

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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