CVE-2022-310: Malicious code in @harrysforge/currency (npm)

@harrysforge/currency Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-310: Malicious code in @harrysforge/currency (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @harrysforge/currency package is an npm package that provides currency conversion functionality. It is commonly used in applications that require currency conversion calculations. This package is vulnerable to a malicious code injection attack, which can compromise the security of the host system and expose any secrets or keys stored on that system.

Vulnerability Detail

The vulnerability originates from a specific version of the @harrysforge/currency package that contains malicious code. If this package is installed or running on a computer, the entire system should be considered compromised. Immediate action is required to rotate any secrets or keys stored on the affected system from a different computer. Although removing the package is recommended, it may not guarantee the complete removal of all malicious software installed by the attacker.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @harrysforge/currency

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

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

Workaround

There is no known workaround for this vulnerability. It is crucial to remove the @harrysforge/currency package and take the necessary steps to secure the affected system.

Conclusion

The @harrysforge/currency package is vulnerable to a malicious code injection attack, which can compromise the security of the host system. It is crucial to remove this package, rotate any secrets or keys stored on the affected system, and monitor for any signs of malicious activity. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @harrysforge/currency →

Share this vulnerability

FAQ

The impact of this vulnerability is severe. Any system with the @harrysforge/currency package installed or running should be considered compromised, and all secrets and keys stored on that system should be rotated immediately.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide the package-lock.json file, and Vulert will alert you in real-time if any open-source vulnerabilities, including this one, are detected.

Removing the @harrysforge/currency package is recommended, but it may not guarantee the complete removal of all malicious software installed by the attacker. It is crucial to rotate any secrets or keys stored on the affected system from a different computer.

No specific patch is available for this vulnerability. The best course of action is to remove the @harrysforge/currency package and take the necessary steps to secure the affected system.

To prevent similar vulnerabilities, it is essential to regularly update and patch all installed packages. Additionally, consider using a vulnerability monitoring tool like Vulert (https://vulert.com) to receive real-time alerts for open-source vulnerabilities in your software.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @harrysforge/currency

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

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