AudioEditor
Audited by Socket on Oct 20, 2026
2 alerts found:
Anomalyx2SUSPICIOUS. The core audio-editing workflow is coherent and the named credentials fit the purpose, with vendor data flows apparently going to official Anthropic and Cleanvoice services. However, the mandatory pre-task POST to a plaintext localhost service is unnecessary for audio editing, customization files can alter behavior, and the actual Tools/*.ts code is missing, so the true handling of audio and API keys cannot be verified. This looks more like a moderately risky, partially unverifiable workflow than confirmed malware.
No strong indicators of intentional malware (tracking, exfiltration, credential theft, persistence) are present in this module’s logic. The primary security concern is that it executes multiple shell commands via Bun’s $ helper while interpolating user-controlled file paths (inputFile/outFile/tmpDir) and then performs a recursive deletion (rm -rf) on a directory derived from potentially attacker-influenced --output. Additionally, it uses JSON.parse on files produced/read from disk without validation, which can cause crashes/DoS on malformed content. Treat this as a CLI utility that should be hardened against untrusted argv usage (avoid shell interpolation; validate/normalize and constrain paths; replace rm -rf with safer directory cleanup).