How severe is GHSA-pjxp-f379-6284?

No CVSS score has been assigned to GHSA-pjxp-f379-6284 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pjxp-f379-6284?

GHSA-pjxp-f379-6284 affects the following packages: @fangrong/xoc (npm). Ecosystems affected: npm.

How do I fix GHSA-pjxp-f379-6284?

No patched version of @fangrong/xoc has shipped for GHSA-pjxp-f379-6284 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-pjxp-f379-6284 in my npm dependencies?

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

How do I mitigate GHSA-pjxp-f379-6284 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-pjxp-f379-6284 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pjxp-f379-6284 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-pjxp-f379-6284 published, and has it been updated?

GHSA-pjxp-f379-6284 was published on September 3, 2020 and was last updated on July 27, 2023. 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 Package in @fangrong/xocGHSA-pjxp-f379-6284

GHSA-pjxp-f379-6284 is a security vulnerability in @fangrong/xoc. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Jul 27, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 27, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

@fangrong/xocnpm

5downloads / week

Description

Version 1.0.6 of @fangrong/xoc contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Recommendation

Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.

Users may consider downgrading to version 1.0.5

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@fangrong/xoc`	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 @fangrong/xoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of @fangrong/xoc has shipped for GHSA-pjxp-f379-6284 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

Version 1.0.6 of `@fangrong/xoc` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised. Users may consider downgrading to version 1.0.5

O3 Security · Impact-Aware SCA

Is GHSA-pjxp-f379-6284 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works