How severe is GHSA-fgp6-8g62-qx6w?

GHSA-fgp6-8g62-qx6w has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fgp6-8g62-qx6w?

GHSA-fgp6-8g62-qx6w affects the following packages: smartsearchwp (npm). Ecosystems affected: npm.

How do I fix GHSA-fgp6-8g62-qx6w?

No patched version of smartsearchwp has shipped for GHSA-fgp6-8g62-qx6w 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-fgp6-8g62-qx6w in my npm dependencies?

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

How do I mitigate GHSA-fgp6-8g62-qx6w 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-fgp6-8g62-qx6w actively exploited in the wild?

No public exploit code has been indexed for GHSA-fgp6-8g62-qx6w 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-fgp6-8g62-qx6w published, and has it been updated?

GHSA-fgp6-8g62-qx6w was published on September 3, 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 smartsearchwpGHSA-fgp6-8g62-qx6w

CRITICAL

GHSA-fgp6-8g62-qx6w is a critical-severity (CVSS 9.8) vulnerability in smartsearchwp. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 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.

smartsearchwpnpm

5downloads / week

Description

All versions of smartsearchwp contain malicious code. The package is malware intended to steal credentials from websites it is loaded in. It traverses DOM elements looking for fields such as username and password and uploads it to a remote server. The package also port-scans the local gateway and uploads the information to the remote server. It has a feature to fetch commands from the remote server and execute them with eval. The npm security team analysis found several bugs in the malware that prevent it from actually performing its actions. The malicious code is also not invoked upon installation or require; it would require transpiling TypeScript code and using it in a website.

Recommendation

Remove the package from your environment. There is no indication of further compromise.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`smartsearchwp`	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 smartsearchwp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of smartsearchwp has shipped for GHSA-fgp6-8g62-qx6w 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 `smartsearchwp` contain malicious code. The package is malware intended to steal credentials from websites it is loaded in. It traverses DOM elements looking for fields such as `username` and `password` and uploads it to a remote server. The package also port-scans the local gateway and uploads the information to the remote server. It has a feature to fetch commands from the remote server and execute them with `eval`. The npm security team analysis found several bugs in the malware that prevent it from actually performing its actions. The malicious code is also not invoked upon

O3 Security · Impact-Aware SCA

Is GHSA-fgp6-8g62-qx6w in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works