Which versions of aqueduct-client are malicious?

The following RubyGems versions of aqueduct-client are flagged malicious: 1.3.3. Treat any of these as compromised.

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

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

If aqueduct-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.

How do I find aqueduct-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aqueduct-client (version 1.3.3).

Malicious package

aqueduct-clientRubyGems

aqueduct-client is a confirmed malicious RubyGems package (MAL-2025-46893) that executes malicious code on install (malicious version 1.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aqueduct-client (RubyGems)

MAL-2025-46893

Immediate action

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

gem uninstall aqueduct-client

What this malware does

The OpenSSF Package Analysis project identified 'aqueduct-client' @ 1.3.3 (rubygems) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.3.3

Indicators of compromise (SHA-256)

379fca058a380a033332183e2ff704c2c9364d08fc8d550eb7a1f5171bc9221f

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks aqueduct-client-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