other
- Location
install.sh:19- Finding
Undisclosed Installation Telemetry
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This transcription skill is incomplete and makes undisclosed install-time changes and telemetry calls that users should review before installing.
Review this skill carefully before installing. It may be intended for transcription, but this package does not include the actual transcribe executable, makes a persistent change to your zsh startup file, and sends an install analytics request to Signal Loom. Do not rely on the local-only privacy claim until the publisher supplies the missing executable and clearly documents whether audio, video, or metadata are uploaded.
install.sh:19Undisclosed Installation Telemetry
install.sh:16Persistent and Unmanaged Shell Configuration Modification
package.json:4Missing Declared Executable and Contradictory Privacy Claims
A description-behavior mismatch is dangerous because users may trust privacy and local-processing claims while the actual implementation performs unrelated install-time actions such as shell profile modification and outbound telemetry. That combination can conceal unexpected persistence, environment tampering, or data disclosure under the cover of a benign transcription feature.
The skill advertises executable capability via a required binary but declares no explicit tool scope or permissions boundary. In agent environments, undeclared shell-capable behavior weakens reviewability and can let a seemingly simple content skill invoke local commands without clear user or platform constraints.
The skill claims local privacy benefits while also referencing use of a vendor API, but it does not warn users that media or metadata may leave the device depending on how the API is used. For transcription workflows, audio and video frequently contain sensitive personal or business information, so omission of off-device transfer risk can lead to unintended data exposure.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
LOCAL_BIN="${HOME}/.local/bin"
echo "Installing ${SKILL_NAME}..."
mkdir -p "$OPENCLAW_SKILLS" "$LOCAL_BIN"
# Symlink into OpenClaw skills dir
ln -sf "$SCRIPT_DIR" "$OPENCLAW_SKILLS/${SKILL_NAME}"
Appending to ~/.zshrc without notice or confirmation is an unsafe installation practice because it creates persistent environmental changes outside the core transcription function. Silent profile modification reduces user control and can be abused in other contexts to establish persistence or influence future command execution.
The installer silently sends a network telemetry event to a remote endpoint during installation, which contradicts the privacy-oriented framing of the skill and creates an undisclosed data flow. Even though the payload shown is limited to skill/version/source, silent outbound communication during install erodes trust and can expose metadata such as IP address and install timing to the vendor.
The installer performs an undisclosed analytics POST in the background, so users may never notice that installation triggers a remote call. This is dangerous from a privacy and supply-chain trust perspective because installers should minimize hidden side effects, especially network egress unrelated to the core install action.
The hardcoded remote API endpoint indicates install-time communication with a vendor-controlled service. In context, this is not remote code execution, but it is still a real privacy and transparency issue because the installer reaches out to the network for analytics rather than essential operation.
grep -q '~/.local/bin' "${HOME}/.zshrc" 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> "${HOME}/.zshrc"
# Fire install ping (no auth — tracks community installs)
curl -s -m 5 -X POST "https://api.signalloomai.com/v1/analytics/install" \
-H "Content-Type: application/json" \
-d "{\"skill\":\"${SKILL_SLUG}\",\"version\":\"${VERSION}\",\"source\":\"clawhub\"}" &
The hardcoded remote API endpoint indicates install-time communication with a vendor-controlled service. In context, this is not remote code execution, but it is still a real privacy and transparency issue because the installer reaches out to the network for analytics rather than essential operation.
grep -q '~/.local/bin' "${HOME}/.zshrc" 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> "${HOME}/.zshrc"
# Fire install ping (no auth — tracks community installs)
curl -s -m 5 -X POST "https://api.signalloomai.com/v1/analytics/install" \
-H "Content-Type: application/json" \
-d "{\"skill\":\"${SKILL_SLUG}\",\"version\":\"${VERSION}\",\"source\":\"clawhub\"}" &
The installer modifies the user's shell startup file to prepend ~/.local/bin to PATH without warning or confirmation. While commonly done for convenience, persistent shell configuration changes are security-sensitive because they alter command resolution for future sessions and may have unintended side effects.
No suspicious patterns detected.