Which versions of @coralxyz/anchor are malicious?

The following npm versions of @coralxyz/anchor are flagged malicious: 0.30.2. Treat any of these as compromised.

How do I remediate @coralxyz/anchor if I installed it?

@coralxyz/anchor is a typosquat — you almost certainly intended a legitimately-named package. Remove @coralxyz/anchor, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @coralxyz/anchor — how do I know if it already compromised me?

If @coralxyz/anchor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @coralxyz/anchor part of a known attack campaign?

Yes — @coralxyz/anchor is associated with the IN-MAL-2026-017197 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 @coralxyz/anchor across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @coralxyz/anchor (version 0.30.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @coralxyz/anchor across your stack and pipelines.

Malicious package

@coralxyz/anchornpm

@coralxyz/anchor is a confirmed malicious npm package (MAL-2026-13629) that typosquats a legitimate package to trick installs (malicious version 0.30.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @coralxyz/anchor (npm)

MAL-2026-13629

Immediate action

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

npm uninstall @coralxyz/anchor

What this malware does

Package @coralxyz/anchor impersonates the legitimate Solana Anchor framework package @coral-xyz/anchor (hyphen removed). The npm postinstall hook, implemented in scripts/postinstall.js, hides all string literals behind a hex-escaped string-array decoder (_0x5a2f / _0xf). On Windows (win32), the decoded logic downloads a zip archive from the anonymous file host https://files.catbox.moe/9bppy2.zip, extracts it via PowerShell Expand-Archive to a temporary directory, walks the extracted tree, and spawns any.exe file it finds detached with windowsHide. index.js is a minimal stub; the package's advertised Anchor framework functionality is not present, and the postinstall dropper is the sole meaningful behavior. The delivery vector is name confusion with the widely used @coral-xyz/anchor package.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

1475ce579e5b1ce9d7597187d091b29b70cbe1a563ed70946517673c29683763

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @coralxyz/anchor (version 0.30.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @coralxyz/anchor across your stack and pipelines.
If you installed it — respond
@coralxyz/anchor is a typosquat — you almost certainly intended a legitimately-named package. Remove @coralxyz/anchor, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @coralxyz/anchor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @coralxyz/anchor before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @coralxyz/anchor on npm has been identified as a malicious package (version 0.30.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017197

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @coralxyz/anchor-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