interactive-debugging

No overt malware behaviors are present in this module (no code execution, no external network calls, no credential harvesting, no dynamic payload loading). However, it contains intentionally risky debug functionality: an unauthenticated POST /debug endpoint that persists arbitrary request bodies to disk with no redaction or size limits, combined with permissive CORS headers. If exposed to untrusted clients or routed into web/browser contexts, this can lead to sensitive data being logged and potential disk/availability impact via large or high-rate payloads. Primary risk is unsafe debug data persistence, not intentional compromise.