GHSA-gmjp-776j-2394: Ripmed160 Malicious Package Vulnerability

CRITICAL
Share
CVSS 9.1
CWE-506
Published
Advisory Summary

GHSA-gmjp-776j-2394 is a CRITICAL (CVSS 9.1) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Ripmed160 libraries in the npm ecosystem. The issue involves malicious package in ripmed160. Remediation is available in the latest vendor maintenance releases.

GHSA-gmjp-776j-2394 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-gmjp-776j-2394
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Ripmed160
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-gmjp-776j-2394

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

ripmed160 fixed: Latest secure release 
npm install ripmed160@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 ripmed160

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-gmjp-776j-2394, inspect your project dependencies using npm:

npm ls ripmed160

Analyze the terminal output to locate any version of Ripmed160 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 ripmed160 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 CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Ripmed160, 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

All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets. ## Recommendation 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.

GHSA-gmjp-776j-2394 Affected Ripmed160 Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
ripmed160
npm/ripmed160
npm
≥ 0.0.0

References

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

Frequently Asked Questions

What is GHSA-gmjp-776j-2394?
GHSA-gmjp-776j-2394 is a security vulnerability in Ripmed160 involving Malicious Package in ripmed160 under CWE-506: Embedded Malicious Code.
Which Ripmed160 versions are affected?
Affected versions include releases prior to current release patches across affected packages: ripmed160.
What version fixes GHSA-gmjp-776j-2394?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is ripmed160 affected?
Yes, ripmed160 is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-gmjp-776j-2394?
GHSA-gmjp-776j-2394 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with GHSA-gmjp-776j-2394?
GHSA-gmjp-776j-2394 is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-gmjp-776j-2394?
Run the dependency tree command: 'npm ls ripmed160'. 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-gmjp-776j-2394",
  "modified" : "2021-10-01T21:04:56Z",
  "published" : "2020-09-03T17:04:24Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in ripmed160",
  "details" : "All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.\n\n\n## Recommendation\n\nAny 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.\n\nThe 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "ripmed160"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1405"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:58:08Z",
    "nvd_published_at" : null
  }
}