How severe is GHSA-j8qr-rvcv-crhv?

No CVSS score has been assigned to GHSA-j8qr-rvcv-crhv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8qr-rvcv-crhv?

GHSA-j8qr-rvcv-crhv affects the following packages: electron-native-notify (npm). Ecosystems affected: npm.

How do I fix GHSA-j8qr-rvcv-crhv?

No patched version of electron-native-notify has shipped for GHSA-j8qr-rvcv-crhv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-j8qr-rvcv-crhv in my npm dependencies?

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

How do I mitigate GHSA-j8qr-rvcv-crhv 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-j8qr-rvcv-crhv actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8qr-rvcv-crhv 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-j8qr-rvcv-crhv published, and has it been updated?

GHSA-j8qr-rvcv-crhv was published on September 11, 2020 and was last updated on August 31, 2020. 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

Malicious Package in electron-native-notifyGHSA-j8qr-rvcv-crhv

GHSA-j8qr-rvcv-crhv is a security vulnerability in electron-native-notify. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

electron-native-notifynpm

4downloads / week

Description

All versions of electron-native-notify contain malicious code. The package was part of a targeted attack to steal cryptocurrency wallet seeds and upload them to a remote server, effectively giving attackers access to users wallets.

Recommendation

Remove the package from your environment and follow the recommendations by Komodo

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron-native-notify`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron-native-notify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of electron-native-notify has shipped for GHSA-j8qr-rvcv-crhv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

All versions of `electron-native-notify` contain malicious code. The package was part of a targeted attack to steal cryptocurrency wallet seeds and upload them to a remote server, effectively giving attackers access to users wallets. ## Recommendation Remove the package from your environment and [follow the recommendations by Komodo](https://komodoplatform.com/vulnerability-discovered-in-komodos-agama-wallet-this-is-what-you-need-to-do/)

O3 Security · Impact-Aware SCA

Is GHSA-j8qr-rvcv-crhv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works