T09 · Insecure Skill Coding Practices
- Location
SKILL.md:139- Finding
Reusable SMTP Credentials Are Transmitted to a Third-Party Invoice Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent invoice API, but it asks users to send invoice data and optional SMTP passwords to a third-party service without enough disclosure or handling safeguards.
Review this carefully before installing. Use it only if you are comfortable sending invoice contents, customer details, tax IDs, bank/payment fields, and possibly SMTP credentials to ToolWeb. Avoid sending reusable mailbox passwords; prefer a dedicated low-privilege sending account or app-specific credential, and rotate any SMTP password already submitted through this service.
SKILL.md:139Reusable SMTP Credentials Are Transmitted to a Third-Party Invoice Service
The skill enables transmission of sensitive business and personal data—including customer contact details, tax IDs, bank account information, invoice contents, and SMTP credentials—to external services, but the documentation does not clearly warn users about that data flow. This can lead to unintentional disclosure of financial and authentication data to third-party infrastructure, especially when users assume the skill operates locally or only formats documents.
The skill references an external API endpoint, which confirms that user-supplied invoice and email-related data may leave the local environment and be processed by a third-party service. In this context, the transmitted payload can include sensitive financial records, customer PII, tax identifiers, bank details, and possibly SMTP credentials, making external transmission materially security-relevant.
## References
- Kong Route: https://api.toolweb.in/tools/invoicy
- API Docs: https://api.toolweb.in:8165/docs
Natural-language policy checks apply to all file types, including config/spec files. Fields such as 'gstin', 'pan', 'pincode', 'ifsc_code', 'upi_id', and 'is_igst' indicate a specific regional locale, but the spec title and descriptions do not state that this is an India-specific invoice tool or provide any locale opt-in.
This file is a manifest/config type, so vague-trigger checks apply. The root path only uses a generic summary 'Root' and provides no contextual limitation or explicit invocation scope, which makes the activation surface ambiguous rather than narrowly defined.
No suspicious patterns detected.