other
- Location
SKILL.md:43- Finding
Uncontrolled Transmission of Sensitive Data to an External Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is for sharing snippets through snipit.sh, but it normalizes uploading .env files and secrets to an external service without enough warning or safeguards.
Review this before installing. Use it only for material you are allowed to send to snipit.sh, redact secrets and personal data first, avoid uploading .env files or private keys, and do not pass real passwords directly on the command line. Prefer an approved internal sharing or secret-management tool for credentials.
SKILL.md:43Uncontrolled Transmission of Sensitive Data to an External Service
SKILL.md:23Snippet Passwords Exposed Through Command-Line Arguments
SKILL.md:13Unpinned Global Installation of a Third-Party npm Package
The example snipit create .env -t "Config" -p secret -b -e 1h encourages uploading a .env file, which commonly contains API keys, database passwords, and other credentials, to a third-party service. Password protection and burn-after-read reduce exposure but do not eliminate the risk of credential leakage, weak passwords, mishandling, server-side compromise, or policy violations.
cat code.js | snipit -l javascript
# With options
snipit create .env -t "Config" -p secret -b -e 1h
# Get snippet
snipit get abc123 -p secret
This example again normalizes uploading a .env file to an external service under the label 'Secure config,' which may mislead users into believing password protection and burn-after-read make credential sharing safe. In practice, .env files frequently contain production secrets, so the skill context makes this more dangerous by specifically targeting sensitive configuration material.
tail -100 app.log | snipit -e 1h
# Secure config (password + burn)
snipit create .env -p secret123 -b
# Build output
./build.sh 2>&1 | snipit -t "Build log"
The skill explicitly markets sharing 'secrets' and shows examples uploading .env files to snipit.sh, but it does not clearly warn that the data is being transmitted to a third-party external service. Even if the service uses encryption and optional password protection, this can normalize exfiltration of credentials or sensitive configuration outside the local environment.
The curl fallback directly documents posting arbitrary content to https://snipit.sh/api/snippets without any caution that the payload leaves the host and is stored by an external service. This is especially risky because the fallback is low-level and easy to adapt for automated upload of sensitive code, logs, or secrets.
This command performs explicit external transmission of user-supplied content to a third-party HTTPS endpoint. In context, that is the intended function of the skill, but it still represents a real data exfiltration path if used on sensitive code, logs, configs, or secrets.
# Create
curl -X POST https://snipit.sh/api/snippets \
-H "Content-Type: application/json" \
-d '{"content":"code","language":"python","burnAfterRead":true}'
No suspicious patterns detected.