How severe is GHSA-73qr-pfmq-6rp8?

No CVSS score has been assigned to GHSA-73qr-pfmq-6rp8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-73qr-pfmq-6rp8?

GHSA-73qr-pfmq-6rp8 affects the following packages: coa (npm), coa (npm), coa (npm), coa (npm), coa (npm), coa (npm). Ecosystems affected: npm.

How do I fix GHSA-73qr-pfmq-6rp8?

No patched version of coa has shipped for GHSA-73qr-pfmq-6rp8 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-73qr-pfmq-6rp8 in my npm dependencies?

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

How do I mitigate GHSA-73qr-pfmq-6rp8 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-73qr-pfmq-6rp8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-73qr-pfmq-6rp8 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-73qr-pfmq-6rp8 published, and has it been updated?

GHSA-73qr-pfmq-6rp8 was published on November 4, 2021 and was last updated on September 7, 2022. 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

Embedded malware in coaGHSA-73qr-pfmq-6rp8

GHSA-73qr-pfmq-6rp8 is a security vulnerability in coa. No vendor fix is recorded yet; mitigation options are listed below.

Published

Nov 4, 2021

Updated

Sep 7, 2022

Affected

6 pkgs

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 7, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

6 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

374other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

coanpm

6.3Mdownloads / week

Description

The npm package coa had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See this issue for details as they unfold. 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

6 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`coa`	all versions	No fix
📦npm	`coa`	all versions	No fix
📦npm	`coa`	all versions	No fix
📦npm	`coa`	all versions	No fix
📦npm	`coa`	all versions	No fix
📦npm	`coa`	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 coa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of coa has shipped for GHSA-73qr-pfmq-6rp8 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 package `coa` had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/veged/coa/issues/99) for details as they unfold. 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, th

O3 Security · Impact-Aware SCA

Is GHSA-73qr-pfmq-6rp8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works