Critical Malicious Code Vulnerability in oce-freecoin Package

oce-freecoin Updated 21 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-421: Malicious code in oce-freecoin (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 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 oce-freecoin package is an npm library designed for cryptocurrency-related functionalities. It allows developers to integrate freecoin transactions and features into their applications. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the oce-freecoin package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications are severe, as attackers may gain complete control over the affected systems, leading to potential data breaches and loss of integrity.

How To Fix

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

npm uninstall oce-freecoin

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 are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that all sensitive data is rotated and monitored for any unauthorized access.

Conclusion

The oce-freecoin package contains a critical vulnerability due to embedded malicious code, posing severe risks to any system using it. Immediate action is required to remove the package and secure sensitive data. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for oce-freecoin →

Share this vulnerability

FAQ

The oce-freecoin package is an npm library used for integrating cryptocurrency functionalities into applications.

The malicious code can compromise your system, allowing attackers to gain unauthorized access to sensitive information and control over your computer.

You should immediately remove the oce-freecoin package and rotate all secrets and keys stored on your computer.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

The long-term implications include potential data breaches, loss of sensitive information, and compromised system integrity, which can lead to further attacks.

How To Fix

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

npm uninstall oce-freecoin

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