Malicious Code Vulnerability in Sturdyfetch4: A Critical Security Risk

sturdyfetch4 Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192873: Malicious code in sturdyfetch4 (npm). Affects sturdyfetch4 versions 0.30.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 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

Sturdyfetch4 is an npm package designed for efficient data fetching and handling within JavaScript applications. It offers features such as streamlined API calls and enhanced data management capabilities. However, recent findings have revealed that version 0.30.1 of this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in Sturdyfetch4 stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or lead to further exploitation of the system. The malicious nature of this vulnerability was identified by ReversingLabs, highlighting the importance of vigilance when using third-party packages.

How To Fix

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

npm uninstall sturdyfetch4

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

If immediate updating is not feasible, consider removing the package from your project until a secure version is released. You can do this by running: 'npm uninstall sturdyfetch4'. Additionally, monitor your application for any unusual behavior that may indicate exploitation.

Conclusion

The discovery of malicious code in Sturdyfetch4 version 0.30.1 poses a significant threat to applications that utilize this package. It is essential for developers to update to a secure version and remain vigilant against potential exploits. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for sturdyfetch4 →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and execute arbitrary commands within the application.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Consider removing the package from your project and monitoring your application for any unusual behavior until a secure version is available.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat detection and analysis.

Yes, updating to a patched version of Sturdyfetch4 will resolve the vulnerability. Check for the latest version in the npm registry.

How To Fix

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

npm uninstall sturdyfetch4

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