agent-doorbell

This module is not overtly malicious in isolation (no network calls, credential theft, obfuscation, or direct code execution). However, it is an execution-enabling configuration installer: it persists hook commands into agent runtime settings that will later cause the package’s companion hook-runner scripts to run. It includes a security-sensitive PowerShell flag (-ExecutionPolicy Bypass) and allows overriding the node executable (--node-command), increasing misuse risk if an attacker can influence CLI arguments or if the downstream hook execution mechanism is permissive. Risk is best characterized as moderate supply-chain/tooling risk rather than confirmed malware.

Overall, the module behaves like a local status notifier (optional beep and desktop toast/balloon), with DryRun support. The primary supply-chain/security concern is the Windows notification implementation: it dynamically constructs a PowerShell payload, Base64-encodes it, and executes it via Start-Process using -ExecutionPolicy Bypass and -WindowStyle Hidden—an approach commonly associated with stealthy execution. Within this snippet, the executed logic appears limited to showing a NotifyIcon balloon, with no network/filesystem/persistence/credential access. This warrants review/approval and monitoring in a supply-chain context, but the fragment does not provide direct evidence of malware beyond the suspicious execution technique.

This file functions as a cross-platform notification/sound launcher, with no direct evidence of data exfiltration or credential theft in the snippet. However, it executes external interpreters/automation tools: on Windows it runs a bundled PowerShell script with -ExecutionPolicy Bypass (and hidden execution), and on macOS it passes user-influenced strings into an osascript -e code string with only partial escaping. If CLI inputs can be attacker-controlled, these patterns increase the likelihood of unintended script/code execution via the launcher or the bundled ring.ps1. Overall risk is moderate and depends heavily on the contents and behavior of ring.ps1.

This fragment is a thin launcher that silently starts a local helper PowerShell script (ring.ps1) with execution-policy bypass and a hidden window, passing event/status strings as arguments. It contains no direct evidence of exfiltration, credential theft, or destructive behavior in the provided code; however, the combination of hidden execution, suppressed error handling, and execution-policy bypass is a notable stealth pattern. The overall supply-chain risk cannot be fully assessed without reviewing ring.ps1, which is where functional behavior (benign notifications vs. malicious actions) would reside.