How severe is GHSA-38hx-3542-8fh3?

No CVSS score has been assigned to GHSA-38hx-3542-8fh3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-38hx-3542-8fh3?

GHSA-38hx-3542-8fh3 affects the following packages: electorn (npm). Ecosystems affected: npm.

How do I fix GHSA-38hx-3542-8fh3?

No patched version of electorn has shipped for GHSA-38hx-3542-8fh3 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-38hx-3542-8fh3 in my npm dependencies?

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

How do I mitigate GHSA-38hx-3542-8fh3 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-38hx-3542-8fh3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-38hx-3542-8fh3 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-38hx-3542-8fh3 published, and has it been updated?

GHSA-38hx-3542-8fh3 was published on October 1, 2020 and was last updated on October 1, 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 code in `electorn`GHSA-38hx-3542-8fh3

GHSA-38hx-3542-8fh3 is a security vulnerability in electorn. No vendor fix is recorded yet; mitigation options are listed below.

Published

Oct 1, 2020

Updated

Oct 1, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 1, 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.

electornnpm

12downloads / week

Description

npm packages loadyaml and electorn were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:

IP and IP-based geolocation
home directory name
local username

The malicious packages have been removed from the npm registry and the leaked content removed from GitHub.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electorn`	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 electorn, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of electorn has shipped for GHSA-38hx-3542-8fh3 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

npm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information: - IP and IP-based geolocation - home directory name - local username The malicious packages have been removed from the npm registry and the leaked content removed from GitHub.

O3 Security · Impact-Aware SCA

Is GHSA-38hx-3542-8fh3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works