Malicious code in stake-api (npm)

stake-api Updated 02 Oct 2025

Summary

06/04/2024
CRITICAL
No i
Critical
Not published

MAL-2024-1253: Malicious code in stake-api (npm). Affects stake-api versions 1.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The stake-api package is an npm package that provides functionality for interacting with a stake API. It is commonly used in applications that involve staking and delegating tokens. The package allows developers to easily integrate staking functionality into their applications. However, the package has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The stake-api package has been flagged as malicious due to the following reasons:

  • The package communicates with a domain associated with malicious activity.
  • The package executes one or more commands associated with malicious behavior.

This malicious code poses a significant security risk to applications that use the stake-api package. It can potentially lead to unauthorized access, data breaches, and other malicious activities.

How To Fix

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

npm uninstall stake-api

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 specific workaround mentioned for this vulnerability. The best course of action is to remove the stake-api package and replace it with a trusted alternative.

Conclusion

The stake-api package has been identified as malicious and poses a significant security risk to applications that use it. It is crucial to remove the package and replace it with a trusted alternative to ensure the integrity and security of the application. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for stake-api →

Share this vulnerability

FAQ

Stake-api is an npm package that provides functionality for interacting with a stake API. It is commonly used in applications that involve staking and delegating tokens.

The stake-api package has been flagged as malicious because it communicates with a domain associated with malicious activity and executes commands associated with malicious behavior.

Using the stake-api package can pose significant security risks, including unauthorized access, data breaches, and other malicious activities.

To fix the vulnerability, it is recommended to remove the stake-api package from your application and replace it with a trusted alternative. Additionally, perform a thorough security audit of your codebase.

There are no specific workarounds mentioned for this vulnerability. The best course of action is to remove the stake-api package and replace it with a trusted alternative.

How To Fix

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

npm uninstall stake-api

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