What does the coral-dev-proxy malware do?

The package coral-dev-proxy was found to contain malicious code. The OpenSSF Package Analysis project identified 'coral-dev-proxy' @ 99.9.2 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of coral-dev-proxy are malicious?

The following npm versions of coral-dev-proxy are flagged malicious: 99.9.2, 99.9.3. Treat any of these as compromised.

How do I remediate coral-dev-proxy if I installed it?

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

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

Search your lockfiles and build artifacts for coral-dev-proxy (2 malicious versions).

Malicious package

coral-dev-proxynpm

Advisory published May 8, 2026Updated May 12, 2026

coral-dev-proxy is a confirmed malicious npm package (MAL-2026-3395) that executes malicious code on install (malicious versions 99.9.2, 99.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in coral-dev-proxy (npm)

MAL-2026-3395

Immediate action

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

npm uninstall coral-dev-proxy

What this malware does

The package coral-dev-proxy was found to contain malicious code.

The OpenSSF Package Analysis project identified 'coral-dev-proxy' @ 99.9.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

99.9.299.9.3

Indicators of compromise (SHA-256)

43201e77d986713200b2c3f3de10a94b94d87a3d86183e8c6a203533fc32346f

72404a2fb27337386b313984f096fd93c14ba8fad384d1881772c6b3b725c5c4

938459f8d0b02585c73f8dedee34a7e499784f290f4c9cabf61706eeda5bbfe1

Detection & response playbook

Malicious package

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