How severe is GHSA-84c3-j8r2-mcm8?

GHSA-84c3-j8r2-mcm8 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-84c3-j8r2-mcm8?

GHSA-84c3-j8r2-mcm8 affects the following packages: @nfid/embed (npm). Ecosystems affected: npm.

How do I fix GHSA-84c3-j8r2-mcm8?

Update @nfid/embed to 0.10.1-alpha.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84c3-j8r2-mcm8 is resolved across your whole dependency graph.

How do I detect GHSA-84c3-j8r2-mcm8 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nfid/embed, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-84c3-j8r2-mcm8 if there is no patch (or I can't update yet)?

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.

Is GHSA-84c3-j8r2-mcm8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-84c3-j8r2-mcm8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-84c3-j8r2-mcm8 published, and has it been updated?

GHSA-84c3-j8r2-mcm8 was published on February 26, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

@nfid/embed has compromised private key due to @dfinity/auth-client producing insecure session keysGHSA-84c3-j8r2-mcm8

CRITICAL

GHSA-84c3-j8r2-mcm8 is a critical-severity (CVSS 9.1) vulnerability in @nfid/embed. A fix is available for @nfid/embed — see the affected versions and patch details below.

Published

Feb 26, 2024

Updated

Feb 26, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 26, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@nfid/embednpm

78downloads / week

Description

Problem

User sessions in the @nfid/embed SDK with Ed25519 keys are vulnerable due to a compromised private key 535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe. This exposes users to potential loss of funds on ledgers and unauthorized access to canisters they control.

Solution

Using version >1.0.1 of @dfinity/auth-client and @dfinity/identity packages, or @nfid/embed >0.10.1-alpha.6 includes patched versions of the issue.

User sessions will be automatically fixed when they re-authenticate.

Why this happened

The DFINITY auth client library provides a function, Ed25519KeyIdentity.generate, for generating an Ed25519 key pair. This function includes an optional parameter to supply a 32-byte seed value, which will be utilized as the secret key. In cases where no seed value is provided, the library is expected to generate the secret key using secure randomness. However, a recent update of DFINITY libraries has compromised this assurance by employing an insecure seed for key pair generation.

References

AgentJS CVE

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@nfid/embed`	≥ 0.10.0&&< 0.10.1-alpha.6	0.10.1-alpha.6`npm install @nfid/embed@0.10.1-alpha.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nfid/embed, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nfid/embed to 0.10.1-alpha.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84c3-j8r2-mcm8 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.

Frequently Asked Questions

### Problem User sessions in the @nfid/embed SDK with Ed25519 keys are vulnerable due to a compromised private key `535yc-uxytb-gfk7h-tny7p-vjkoe-i4krp-3qmcl-uqfgr-cpgej-yqtjq-rqe`. This exposes users to potential loss of funds on ledgers and unauthorized access to canisters they control. ### Solution Using version >1.0.1 of @dfinity/auth-client and @dfinity/identity packages, or @nfid/embed >0.10.1-alpha.6 includes patched versions of the issue. User sessions will be automatically fixed when they re-authenticate. ### Why this happened The DFINITY auth client library provides a function, `E

O3 Security · Impact-Aware SCA

Is GHSA-84c3-j8r2-mcm8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works