Which versions of @ensdomains/curvearithmetics are malicious?

The following npm versions of @ensdomains/curvearithmetics are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @ensdomains/curvearithmetics if I installed it?

@ensdomains/curvearithmetics is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @ensdomains/curvearithmetics — how do I know if it already compromised me?

If @ensdomains/curvearithmetics 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 @ensdomains/curvearithmetics part of a known attack campaign?

Yes — @ensdomains/curvearithmetics is associated with the GHSA-x7jj-9j59-3wx8 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 @ensdomains/curvearithmetics 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 @ensdomains/curvearithmetics (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/curvearithmetics across your stack and pipelines.

Malicious package

@ensdomains/curvearithmeticsnpm

Malicious code in @ensdomains/curvearithmetics (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190726

Immediate action

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

npm uninstall @ensdomains/curvearithmetics

What this malware does

The package @ensdomains/curvearithmetics 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

f9b9321bba54bb833445dfe4a5be9ec3daa202d4a24a33dc553ef1954927bc42

3e8d0412a2e09e5e875c436da127697b8fe370cc878272dc55216b4d6b16d13c

9645ac01e4af4cf68b3dd6947b67c9ab51972ff521f88e4e4543416fbbc1b7c8

a1f2b5dd2c8bf06d6955443e35913a7380a046bf7218f5e6dc9785469e03c246

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ensdomains/curvearithmetics (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/curvearithmetics across your stack and pipelines.
If you installed it — respond
@ensdomains/curvearithmetics is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ensdomains/curvearithmetics 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 @ensdomains/curvearithmetics 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. @ensdomains/curvearithmetics on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x7jj-9j59-3wx8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/curvearithmetics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring