Malicious Package in riped160

riped160 Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.1

GHSA-rwcq-qpm6-7867: Malicious Package in riped160. Affects riped160 versions >= 0.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The riped160 package is an npm package that provides functionality for the RIPEMD-160 cryptographic hash function. It is commonly used in applications that require secure hashing of data. However, all versions of this package were found to contain malware. The package was specifically designed to find and exfiltrate cryptocurrency wallets.

Vulnerability Detail

The presence of malware in the riped160 package poses a significant security risk. Any computer that has this package installed or running should be considered fully compromised. The malware is capable of accessing and stealing cryptocurrency wallets, which can result in financial loss for the affected users. It is important to note that removing the package may not completely eliminate the malicious software, as the attacker may have gained full control of the compromised computer.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The presence of malware in the riped160 package poses a critical security risk, particularly for users who have cryptocurrency wallets on their computers. It is essential to take immediate action by rotating all secrets and keys, removing the package, and conducting a thorough security audit. Keeping software and packages up to date is crucial to prevent future attacks. For further support and assistance, please contact DevNack.com.

See every vulnerability recorded for riped160 →

Share this vulnerability

FAQ

If you have the riped160 package installed on your computer, it is highly likely that your system is compromised. It is recommended to follow the steps mentioned in the 'How to Fix' section to mitigate the risk.

While the primary purpose of the malware is to target cryptocurrency wallets, it is possible that it may also attempt to access other sensitive information on the compromised computer. It is crucial to rotate all secrets and keys stored on the affected system.

Removing the riped160 package is an essential step in mitigating the vulnerability. However, due to the potential full control of the compromised computer by an external entity, there is no guarantee that removing the package will remove all traces of the malicious software. A thorough security audit is recommended.

To prevent future attacks, it is crucial to keep all software and packages up to date. Regularly check for security updates and patches for the software you use. Additionally, practicing good security hygiene, such as using strong and unique passwords, enabling two-factor authentication, and avoiding suspicious downloads, can help mitigate the risk of similar vulnerabilities.

For more information about this vulnerability, you can refer to the GitHub Security Advisory database. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback