You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're using elliptic, which has long been unmaintained, and has a few cases where it produces invalid outputs, which means in blockchain context "users lose money".
It is advised to replace it with audited@noble/curves.
This appears to have been resolved by PR #5577 which replaced elliptic with noble/secp256k1. All direct source code imports of elliptic have been migrated to @noble/curves. The elliptic dependency now only exists as a locked transitive dependency.
elliptic has been unmaintained for years and its invalid-output cases are real. In a custody SDK that is a funds-loss vector, not a hygiene issue. @noble/curves is the audited replacement. Happy to take a look at the relevant code if helpful.
Activity
paulmillr commentedon Feb 17, 2025
Do you guys still care about security?
Elliptic just had a vulnerability which leaked private keys from signatures GHSA-vjh7-7g9h-fjfh
OttoAllmendinger commentedon Feb 18, 2025
thank you for pointing this out
#5577
michaelchenchen commentedon Feb 14, 2026
This appears to have been resolved by PR #5577 which replaced elliptic with noble/secp256k1. All direct source code imports of elliptic have been migrated to @noble/curves. The elliptic dependency now only exists as a locked transitive dependency.
exocognosis commentedon Oct 6, 2026
elliptic has been unmaintained for years and its invalid-output cases are real. In a custody SDK that is a funds-loss vector, not a hygiene issue. @noble/curves is the audited replacement. Happy to take a look at the relevant code if helpful.