Which versions of dopc-client are malicious?

The following RubyGems versions of dopc-client are flagged malicious: 1.0.0, 10.0.0. Treat any of these as compromised.

How do I remediate dopc-client if I installed it?

dopc-client establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed dopc-client — how do I know if it already compromised me?

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

Yes — dopc-client is associated with the IN-MAL-2026-022529, IN-MAL-2026-022530 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 dopc-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dopc-client (2 malicious versions).

Malicious package

dopc-clientRubyGems

Advisory published Nov 3, 2026Updated Nov 3, 2026

dopc-client is a confirmed malicious RubyGems package (MAL-2026-18518) that opens a backdoor for remote access (malicious versions 1.0.0, 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dopc-client (RubyGems)

MAL-2026-18518

Immediate action

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

gem uninstall dopc-client

What this malware does

On require 'dopc-client', lib/dopc-client.rb issues a plaintext HTTP GET to the hardcoded bare IP 38.242.235.206 at path /depconf/dopc-client/require with query parameters carrying the installer's OS username (ENV['USER']), hostname (Socket.gethostname), and current working directory (Dir.pwd). The call fires as a top-level side effect of loading the gem, errors are swallowed, and the destination is a plaintext bare IP unrelated to any declared publisher infrastructure. Inline comments and the gemspec description frame the call as a 'benign beacon' / 'defensive placeholder'; the author-controlled self-label does not change the observed behavior — installer-identifying fields are shipped to a third-party endpoint the caller did not configure or opt into.

Malicious versions

2 flagged

1.0.010.0.0

Indicators of compromise (SHA-256)

0ecbe68fef68472dcc1e9778859b71dcba31c06e8db799d75bb95c013f6ab1da

7d5e44ca4d910ac8b18e5f0cf83fe6d9cbee634ba01c548361071b98c4095c0f

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for dopc-client (2 malicious versions).
If you installed it — respond
dopc-client establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dopc-client 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. dopc-client on RubyGems has been identified as a malicious package (versions 1.0.0, 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022529IN-MAL-2026-022530

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dopc-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database