Which versions of closure-net are malicious?

Every published version of closure-net on npm is considered malicious. Remove the package entirely.

How do I remediate closure-net if I installed it?

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

If closure-net 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.

Is closure-net part of a known attack campaign?

Yes — closure-net is associated with the GHSA-9vx9-5r47-4mxj 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 closure-net across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for closure-net (all published versions).

Malicious package

closure-netnpm

Advisory published Jan 16, 2026Updated Jan 16, 2026

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

Malicious code in closure-net (npm)

MAL-2026-276

Immediate action

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

npm uninstall closure-net

What this malware does

The package closure-net was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

410d3b94b9a6867a17fa4f4cce19f0802ad4055417d675c5d28cc79d68b55468

3499f9af0c0265b25c4a428a4d94e7c58a97c6cf3c6f9c536ef55a99fd041875

Detection & response playbook

Malicious package

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

Campaign

GHSA-9vx9-5r47-4mxj

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks closure-net-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