What does the conduit-utils malware do?

The OpenSSF Package Analysis project identified 'conduit-utils' @ 2.95.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of conduit-utils are malicious?

The following npm versions of conduit-utils are flagged malicious: 2.95.0, 3.99.0. Treat any of these as compromised.

How do I remediate conduit-utils if I installed it?

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

If conduit-utils 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 conduit-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for conduit-utils (2 malicious versions).

Malicious package

conduit-utilsnpm

Advisory published Feb 22, 2026Updated Feb 23, 2026

conduit-utils is a confirmed malicious npm package (MAL-2026-985) that executes malicious code on install (malicious versions 2.95.0, 3.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in conduit-utils (npm)

MAL-2026-985

Immediate action

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

npm uninstall conduit-utils

What this malware does

The OpenSSF Package Analysis project identified 'conduit-utils' @ 2.95.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

2.95.03.99.0

Indicators of compromise (SHA-256)

9f633d16f7a0d621de3ff6221f99ffbc77f942c409d0d2adfbe58307211688bf

fac3bb8f07f1c325e1044ce89971b90f9253dcb11b29e80fa2c50f1a1fbc885f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for conduit-utils (2 malicious versions).
If you installed it — respond
Remove conduit-utils 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 conduit-utils 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. conduit-utils on npm has been identified as a malicious package (versions 2.95.0, 3.99.0 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 conduit-utils-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