Vulnerabilities in pkg:npm/@fangrong/xoc

PACKAGE
Share
Advisory Summary

GHSA-pjxp-f379-6284 is a CRITICAL malicious package vulnerability (General Security Weakness) affecting @fangrong/xoc libraries in the npm ecosystem. The issue involves malicious package in @fangrong/xoc. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@fangrong/xoc

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@fangrong/xoc. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-pjxp-f379-6284 - CRITICAL Malicious Package in @fangrong/xoc

GHSA-pjxp-f379-6284 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-pjxp-f379-6284
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product @fangrong/xoc
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-pjxp-f379-6284

To remediate this vulnerability, upgrade all affected @fangrong/xoc dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@fangrong/xoc fixed: Latest secure release 
npm install @fangrong/xoc@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @fangrong/xoc

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-pjxp-f379-6284, inspect your project dependencies using npm:

npm ls @fangrong/xoc

Analyze the terminal output to locate any version of @fangrong/xoc in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls @fangrong/xoc command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In @fangrong/xoc, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-pjxp-f379-6284 Affected @fangrong/xoc Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
@fangrong/xoc
npm/@fangrong/xoc
npm
1.0.6
All 1 versions
1.0.6
None specified

References

www.npmjs.com/advisories/1104 WEB
https://www.npmjs.com/advisories/1104

Frequently Asked Questions

What is GHSA-pjxp-f379-6284?
GHSA-pjxp-f379-6284 is a security vulnerability in @fangrong/xoc involving Malicious Package in @fangrong/xoc under General Security Weakness.
Which @fangrong/xoc versions are affected?
Affected versions include releases prior to current release patches across affected packages: @fangrong/xoc.
What version fixes GHSA-pjxp-f379-6284?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is @fangrong/xoc affected?
Yes, @fangrong/xoc is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-pjxp-f379-6284?
GHSA-pjxp-f379-6284 is classified under General Security Weakness.
How can I check npm dependencies for GHSA-pjxp-f379-6284?
Run the dependency tree command: 'npm ls @fangrong/xoc'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pjxp-f379-6284",
  "modified" : "2023-07-27T20:15:13Z",
  "published" : "2020-09-03T19:13:27Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in @fangrong/xoc",
  "details" : "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=`\n\n\n\n## Recommendation\n\nRemove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.\n\nUsers may consider downgrading to version 1.0.5",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@fangrong/xoc"
    },
    "versions" : [ "1.0.6" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1104"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:47:24Z",
    "nvd_published_at" : null
  }
}