How severe is GHSA-w8fh-pvq2-x8c4?

No CVSS score has been assigned to GHSA-w8fh-pvq2-x8c4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w8fh-pvq2-x8c4?

GHSA-w8fh-pvq2-x8c4 affects the following packages: sonatype (npm). Ecosystems affected: npm.

How do I fix GHSA-w8fh-pvq2-x8c4?

No patched version of sonatype has shipped for GHSA-w8fh-pvq2-x8c4 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-w8fh-pvq2-x8c4 in my npm dependencies?

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

How do I mitigate GHSA-w8fh-pvq2-x8c4 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-w8fh-pvq2-x8c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w8fh-pvq2-x8c4 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-w8fh-pvq2-x8c4 published, and has it been updated?

GHSA-w8fh-pvq2-x8c4 was published on January 29, 2021 and was last updated on January 29, 2021. 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 npm package: sonatypeGHSA-w8fh-pvq2-x8c4

GHSA-w8fh-pvq2-x8c4 is a security vulnerability in sonatype. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jan 29, 2021

Updated

Jan 29, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jan 29, 2021 · 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.

sonatypenpm

4downloads / week

Description

The npm sonatype package has been identified as malicious and removed from the npm package registry.

Remediation

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sonatype`	≥ 0.0.0	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 sonatype, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of sonatype has shipped for GHSA-w8fh-pvq2-x8c4 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

The npm `sonatype` package has been identified as malicious and removed from the npm package registry. ## Remediation Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

O3 Security · Impact-Aware SCA

Is GHSA-w8fh-pvq2-x8c4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works