Malicious Code Detected in cycle-monorepo-sandbox-http Package

cycle-monorepo-sandbox-http Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17870: Malicious code in cycle-monorepo-sandbox-http (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 cycle-monorepo-sandbox-http package is a Node.js library designed for managing and facilitating HTTP requests within a monorepo structure. It provides developers with tools to streamline their workflow and enhance the efficiency of their applications. However, this package has been found to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the cycle-monorepo-sandbox-http package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The package was introduced without proper vetting, making it susceptible to exploitation by attackers.

How To Fix

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

npm uninstall cycle-monorepo-sandbox-http

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 remove the cycle-monorepo-sandbox-http package from their project until a secure version is released. This can be done using the command: npm uninstall cycle-monorepo-sandbox-http. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the cycle-monorepo-sandbox-http package highlights the importance of vigilance in managing open-source dependencies. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for cycle-monorepo-sandbox-http →

Share this vulnerability

FAQ

It is a Node.js library designed to manage HTTP requests within a monorepo setup, aimed at improving development efficiency.

The malicious code was identified by security researchers from Amazon Inspector, who reported the findings to the community.

Using the compromised package can lead to unauthorized access to sensitive data, potential data breaches, and exploitation of application vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall cycle-monorepo-sandbox-http

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