Which versions of delphoi are malicious?

The following npm versions of delphoi are flagged malicious: 1.8.2. Treat any of these as compromised.

How do I remediate delphoi if I installed it?

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

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

Search your lockfiles and build artifacts for delphoi (version 1.8.2).

Malicious package

delphoinpm

Advisory published Mar 20, 2026Updated Mar 23, 2026

delphoi is a confirmed malicious npm package (MAL-2026-1998) that executes malicious code on install (malicious version 1.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in delphoi (npm)

MAL-2026-1998

Immediate action

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

npm uninstall delphoi

What this malware does

The package delphoi was found to contain malicious code.

The OpenSSF Package Analysis project identified 'delphoi' @ 1.8.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.8.2

Indicators of compromise (SHA-256)

c15c8182b6e392861478887a08b04eb8fecc38b70000313dfaf1cad8ac8bc831

72f68bb459a4772a75900ddec7e0a918b514f2211a2303aa80ef82252078e3b6

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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