Malicious Code Detected in eosio-toppings Package

eosio-toppings Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19694: Malicious code in eosio-toppings (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 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 eosio-toppings package is an npm library designed to extend the functionality of EOSIO-based applications. It provides various utilities and enhancements for developers working within the EOSIO ecosystem. However, it has been identified to contain malicious code that poses a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the eosio-toppings package. This code can compromise the integrity of applications that utilize this package, potentially leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall eosio-toppings

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

As a temporary measure, users can avoid using the eosio-toppings package altogether and seek alternative libraries that provide similar functionality without the associated risks.

Conclusion

The eosio-toppings package has been identified as containing malicious code, posing a serious threat to users. It is crucial for developers to remove this package from their projects and monitor for updates or alternatives. Utilizing tools like Vulert can help maintain security by identifying vulnerabilities in real-time.

See every vulnerability recorded for eosio-toppings →

Share this vulnerability

FAQ

eosio-toppings is an npm package designed to enhance EOSIO applications with additional features and utilities.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks, including potential unauthorized access to user data.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can identify if your application is affected. Visit Vulert Scanner to check without any signup.

You should remove the eosio-toppings package from your project immediately and look for alternative packages that do not have known vulnerabilities.

As of now, there is no patched version available. Users are advised to remove the package until a secure version is released.

How To Fix

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

npm uninstall eosio-toppings

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