Which versions of cors-version are malicious?

The following npm versions of cors-version are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate cors-version if I installed it?

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

I already installed cors-version — how do I know if it already compromised me?

If cors-version 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 cors-version part of a known attack campaign?

Yes — cors-version is associated with the GHSA-2hwp-7m6r-hgjg, IN-MAL-2026-013610, IN-MAL-2026-013606 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 cors-version 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 cors-version (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cors-version across your stack and pipelines.

Malicious package

cors-versionnpm

cors-version is a confirmed malicious npm package (MAL-2026-12026) that typosquats a legitimate package to trick installs (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cors-version (npm)

MAL-2026-12026

Immediate action

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

npm uninstall cors-version

What this malware does

The CommonJS entry of cors-version exports getPlugin(), which returns a function that performs an HTTPS GET against https://api.avax-test.dev/ext/bc/rpc with TLS certificate verification disabled (rejectUnauthorized: false) and passes the response body directly to new Function('require', data)(require). The remotely fetched, unpinned bytes are executed with the installer's require function, giving the operator of api.avax-test.dev arbitrary code execution on any host that loads the package. The ESM sibling entry does not contain this fetch-and-eval sink — it is present only in the CJS variant. The package name 'cors-version' is unrelated to its declared purpose ('zero-dependency SVG utilities'), and the destination host mimics Avalanche testnet infrastructure (avax-test.dev is not an Avalanche-owned domain).

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

baf0c037ff57009bf7a5c8368b01bd5ed8bbb35a99ee3b1e02187b33982677ef

31cc14c2580d133bdc90be1d3db60bb01486f84be98c52aca1277d3507118cd0

f448733f684dccf061914e14adb09c6f7e9a9abee3b5cc805cdff2812514c5f3

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 cors-version (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cors-version across your stack and pipelines.
If you installed it — respond
cors-version is a typosquat — you almost certainly intended a legitimately-named package. Remove cors-version, 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 cors-version 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 cors-version 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. cors-version on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2hwp-7m6r-hgjgIN-MAL-2026-013610IN-MAL-2026-013606

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cors-version-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