Which versions of docdesignproxy4647 are malicious?

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

How do I remediate docdesignproxy4647 if I installed it?

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

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

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

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

Malicious package

docdesignproxy4647RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7641

Immediate action

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

gem uninstall docdesignproxy4647

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

084aa6ee5e0d82b56ce0bc000f2b56ded66591732a0be20c32d745bf978a8c81

2bb73ba6cf8484de12d44751450b0e517f542c1f25f7b30e542ef391578932dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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