Which versions of dogapi_demo are malicious?

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

How do I remediate dogapi_demo if I installed it?

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

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

Yes — dogapi_demo is associated with the RLMA-2024-05671, RLUA-2024-10190, RLUA-2026-08009 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 dogapi_demo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dogapi_demo (version 0.1.0).

Malicious package

dogapi_demoRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

dogapi_demo is a confirmed malicious RubyGems package (MAL-2024-6865) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dogapi_demo (RubyGems)

MAL-2024-6865

Immediate action

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

gem uninstall dogapi_demo

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

801ec4af5ec00dcde8dce09bb22b03f1d5812a7bdd44d6633e41886d9fb1699e

857eb2fccc1b27e4dd53190d8700716893d45c10d45ea2bd040264ea34044b9a

86535ef1d8a0f5c037a937ed778d5130ba8c22b59e1378b1ae1c15db39d2794a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05671RLUA-2024-10190RLUA-2026-08009

References

Credits

ReversingLabs · finder

Detect & block this

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