Critical Malicious Code Vulnerability in exact-ticker Package

exact-ticker Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190697: Malicious code in exact-ticker (npm). Affects exact-ticker versions 0.3.5. 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 exact-ticker package is an npm library designed for tracking and displaying cryptocurrency prices in real-time. It is commonly used in applications that require up-to-date financial information. However, this package has been found to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the exact-ticker package. This code can grant unauthorized access to the system, allowing attackers to control the affected computer fully. As a result, all sensitive information, including secrets and keys, may be exposed. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful.

How To Fix

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

npm uninstall exact-ticker

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

Currently, there are no effective workarounds to mitigate the risks posed by the exact-ticker package. The only recommended action is to uninstall the package and secure your system.

Conclusion

The discovery of malicious code within the exact-ticker package poses a severe risk to any system that has it installed. Immediate action is required to remove the package and secure sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for exact-ticker →

Share this vulnerability

FAQ

The exact-ticker package is an npm library used for tracking cryptocurrency prices in real-time.

The malicious code can grant attackers full control over your system, potentially exposing sensitive information.

You should immediately uninstall the exact-ticker package and rotate any secrets or keys stored on your system.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is crucial to secure your system and rotate any sensitive information.

How To Fix

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

npm uninstall exact-ticker

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