Which versions of gemnasium-gitlab-service are malicious?

The following RubyGems versions of gemnasium-gitlab-service are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.3.0, 0.6.0, 6.0.7, 7.0.0, 7.0.1, 7.0.3, 8.0.0. Treat any of these as compromised.

How do I remediate gemnasium-gitlab-service if I installed it?

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

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

Yes — gemnasium-gitlab-service is associated with the RLMA-2024-05735, RLUA-2024-10254, RLUA-2026-08141 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 gemnasium-gitlab-service across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gemnasium-gitlab-service (16 malicious versions).

Malicious package

gemnasium-gitlab-serviceRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

gemnasium-gitlab-service is a confirmed malicious RubyGems package (MAL-2024-6929) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gemnasium-gitlab-service (RubyGems)

MAL-2024-6929

Immediate action

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

gem uninstall gemnasium-gitlab-service

Malicious versions

16 flagged

0.1.00.1.10.1.20.2.10.2.20.2.30.2.40.2.50.2.60.3.00.6.06.0.77.0.07.0.17.0.38.0.0

Indicators of compromise (SHA-256)

b85e5aa125405afe0b91bea9ce9f136a4f4b67080eafe724cab8cc2f6d3f6498

b6e24723bea31cfa1dcad816a409eaf40f7283e559d2f8b1a4b7ec88a2003fa5

371cd7bed65a17fd603ed68416ad4cc18cbd227ca7ae6b2df3dd798c74b8aa24

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gemnasium-gitlab-service (16 malicious versions).
If you installed it — respond
Remove gemnasium-gitlab-service 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 gemnasium-gitlab-service 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. gemnasium-gitlab-service on RubyGems has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05735RLUA-2024-10254RLUA-2026-08141

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks gemnasium-gitlab-service-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