Which versions of newhackgit1778555882 are malicious?

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

How do I remediate newhackgit1778555882 if I installed it?

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

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

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

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

Malicious package

newhackgit1778555882RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8116

Immediate action

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

gem uninstall newhackgit1778555882

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b6d3da1c65c483537d59eaa38a0b61c4cc26595b6a55c0748954f98467f1540b

c81246a6ac44e2e4f0d63e165854ecdff894ecb1152bf0c5173aed6eff49dfac

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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