Malicious Code in oddsfire-components (npm)

oddsfire-components Updated 02 Oct 2025

Summary

25/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8619: Malicious code in oddsfire-components (npm). Affects oddsfire-components versions 1.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The oddsfire-components package is an npm package that provides components for odds calculation and analysis in sports betting applications. It is commonly used by developers to integrate odds functionality into their applications. However, the package has been identified as containing malicious code.

Vulnerability Detail

The oddsfire-components package at version 1.0.1 has been flagged as malicious due to its communication with a domain associated with malicious activity. This indicates that the package may be compromised and could potentially introduce security risks to applications that use it. The malicious code could be used to perform unauthorized actions, steal sensitive information, or compromise the overall security of the application.

How To Fix

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

npm uninstall oddsfire-components

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 essential to remove the oddsfire-components package and follow the recommended steps for remediation.

Conclusion

The oddsfire-components package at version 1.0.1 has been identified as containing malicious code. To ensure the security of your application, it is crucial to remove the package and follow the recommended steps for remediation. If you require further support or assistance in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for oddsfire-components →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

Using the oddsfire-components package with this vulnerability can expose your application to various risks, including unauthorized actions performed by the malicious code, theft of sensitive information, and compromise of your application's overall security. It is crucial to remove the package to mitigate these risks.

Yes, there are several alternative packages available for odds calculation and analysis. It is recommended to research and choose packages from trusted sources with a good track record of security and reliability.

Yes, it is highly recommended to report this vulnerability to the package maintainer. They should be made aware of the issue so that they can take appropriate actions to address it and protect other users of the package.

After removing the oddsfire-components package, it is important to thoroughly scan your application for any signs of compromise. Additionally, consider implementing security best practices such as regular vulnerability scanning, code reviews, and keeping dependencies up to date to minimize the risk of future vulnerabilities.

How To Fix

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

npm uninstall oddsfire-components

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