How severe is GHSA-qv78-398w-cxp7?

GHSA-qv78-398w-cxp7 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qv78-398w-cxp7?

GHSA-qv78-398w-cxp7 affects the following packages: shrugging-logging (npm). Ecosystems affected: npm.

How do I fix GHSA-qv78-398w-cxp7?

No patched version of shrugging-logging has shipped for GHSA-qv78-398w-cxp7 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-qv78-398w-cxp7 in my npm dependencies?

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

How do I mitigate GHSA-qv78-398w-cxp7 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-qv78-398w-cxp7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qv78-398w-cxp7 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-qv78-398w-cxp7 published, and has it been updated?

GHSA-qv78-398w-cxp7 was published on September 11, 2020 and was last updated on September 30, 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

CRITICAL severity

Malicious Package in shrugging-loggingGHSA-qv78-398w-cxp7

CRITICAL

GHSA-qv78-398w-cxp7 is a critical-severity (CVSS 9.8) vulnerability in shrugging-logging. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 11, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 30, 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.

shrugging-loggingnpm

4downloads / week

Description

All versions of shrugging-logging contain malicious code as a postinstall script. The package fetches all names of npm packages owned by the user and attempts to add another maintainer to every package as a means of package hijacking,

Recommendation

Remove the package from your system. If you own any packages that were compromised please contact npm security immediately at [email protected]. Also enable 2FA for publishing to further secure packages you maintain.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`shrugging-logging`	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 shrugging-logging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of shrugging-logging has shipped for GHSA-qv78-398w-cxp7 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 `shrugging-logging` contain malicious code as a postinstall script. The package fetches all names of npm packages owned by the user and attempts to add another maintainer to every package as a means of package hijacking, ## Recommendation Remove the package from your system. If you own any packages that were compromised please contact npm security immediately at [email protected]. Also enable 2FA for publishing to further secure packages you maintain.

O3 Security · Impact-Aware SCA

Is GHSA-qv78-398w-cxp7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works