GHSA-8f9f-pc5v-9r5h is a high-severity (CVSS 8.7) CWE-285 vulnerability in @ensdomains/ens. O3 Security confirms whether GHSA-8f9f-pc5v-9r5h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Malicious takeover of previously owned ENS names
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@ensdomains/ensnpmDescription
Impact
A user who owns an ENS domain can set a "trapdoor", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.
Patches
A new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e.
Workarounds
Do not accept transfers of ENS domains from other users on the old registrar.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @ensdomains/ens | all versions | 0.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @ensdomains/ens. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @ensdomains/ens to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8f9f-pc5v-9r5h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8f9f-pc5v-9r5h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-8f9f-pc5v-9r5h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8f9f-pc5v-9r5h in your dependencies?
O3 detects GHSA-8f9f-pc5v-9r5h across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.