Which versions of htmlmetaproxyzz are malicious?

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

How do I remediate htmlmetaproxyzz if I installed it?

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

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

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

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

Malicious package

htmlmetaproxyzzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7767

Immediate action

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

gem uninstall htmlmetaproxyzz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7e68a6f7953f10d4b55a6bc0fb5ae67795d46aea7846881597df6690e2959edd

01567556a57472b70554231ba7e7dd71ec173f288f0ce6ccfc9c0f55acf9a8d6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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