Please do not open a public issue for security vulnerabilities.

Report privately through one of:

• GitHub Security Advisories — open a private report (preferred).
• Email — 42860185+mukul975@users.noreply.github.com.

Include: a description, affected version/commit, reproduction steps, and impact. Please redact any API keys and do not attach live malware samples or real malware hashes.

You can expect an acknowledgement within 3 business days. We will work with you on a fix and coordinate disclosure once a patch is available; credit is offered unless you prefer to remain anonymous.

This file is also the preferred contact method for any third-party abuse inquiries.

This project is pre-1.0 and ships from main. Security fixes land on main and the latest tagged release.

malware-sandbox-mcp is a client that relays files, URLs and indicators to third-party cloud sandboxes and threat-intelligence APIs. Specifically:

• This repository contains no live malware samples. All tests use mocked HTTP responses (respx); no sample is ever submitted from CI or the test suite.
• No malware is executed locally. Detonation happens entirely inside the third-party sandbox. The server only uploads, polls, and downloads results.
• download_sample retrieves live malware to disk when explicitly acknowledged (acknowledge_malware_download=true). Files are written to a quarantine directory and never executed. MalwareBazaar downloads arrive zip-encrypted with the password infected. Handle these only in an isolated/quarantined environment.
• Sandbox-derived content is untrusted. File names, signatures, domains and other report strings are attacker-controlled and may contain prompt-injection text. The server passes them through strictly as data.
• BYOK only. The server bundles no API keys; each user supplies their own via environment variables and is bound directly by each provider's Terms of Service.

• Key/secret leakage paths, unsafe handling of downloaded artifacts, SSRF or request smuggling in the client layer, prompt-injection handling regressions, dependency vulnerabilities.

• Vulnerabilities in the upstream sandbox/intel services themselves (report to those vendors).
• Misuse of the tool against systems you are not authorized to test.