T08 · Insecure Dependencies
- Location
Skill.md:17- Finding
Unpinned Global Installation of a Third-Party Package
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a disclosed Prismer Cloud integration, but it handles API keys and tokens in ways users should review carefully before installing.
Install only if you trust Prismer Cloud and are comfortable giving this CLI account-scoped credentials. Prefer an anonymous setup or a scoped, revocable API key; avoid pasting secrets into normal chat, rotate any key exposed this way, check permissions on ~/.prismer/config.toml, and consider installing a pinned SDK version instead of the unpinned global command.
Skill.md:17Unpinned Global Installation of a Third-Party Package
Skill.md:25Credentials Passed Through Chat and Command-Line Arguments and Stored in Plaintext Configuration
The skill explicitly instructs the user to share a raw API key with the agent, which is a credential-handling anti-pattern. In an agent setting, this is dangerous because the key may be exposed in logs, chat history, telemetry, downstream tools, or prompt context, enabling unauthorized use of the user's account and services.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
prismer files presign report.pdf --mime application/pdf
# 2. Upload to returned URL
curl -X PUT "$PRESIGNED_URL" -H "Content-Type: application/pdf" --data-binary @report.pdf
# 3. Confirm
prismer files confirm <upload-id>
The skill documents storage of API keys and JWTs in a local config file without any warning about filesystem protections, token sensitivity, or rotation. This increases the chance that credentials are left readable by other local users, included in backups, committed to source control, or exfiltrated by other tools on the host.