Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md `tools/serper_search.js`
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Serper.dev Google search integration with expected API-key and network use, though users should avoid sending sensitive queries to the search provider.
Install only if you are comfortable routing search queries through Serper.dev/Google and exposing a Serper API key to the runtime. Do not put secrets, private customer data, or confidential internal terms into search queries unless that external disclosure is acceptable for your environment.
Referenced artifact was not completely inspected
`tools/serper_search.js`
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
const apiKey = process.env.SERPER_API_KEY;
if (!apiKey) {
throw new Error('SERPER_API_KEY not found in environment. Add it to your .env or TOOLS.md');
}
if (!params.q) {
The skill declares an environment variable requirement but does not define an explicit tool scope such as permissions or allowed-tools. This weakens least-privilege boundaries and makes it harder for the host system to constrain what the skill may access, which can lead to unintended secret exposure or broader execution than expected.
The manifest description says to use the skill whenever you need to "perform web searches, find information online, or research topics," which is a very broad activation scope. It does not provide specific trigger phrases, exclusions, or constraints, so the skill could be invoked for many ordinary user requests without clear boundaries.
The documentation omits a clear warning that user queries are transmitted to the third-party Serper.dev service. This can cause operators or users to unknowingly send sensitive prompts, internal names, credentials, or regulated data to an external API, creating privacy, compliance, and data-leakage risk.
This tool sends user-supplied search queries to the third-party Serper API, which is an external data disclosure boundary. That is a real privacy/security concern because queries may contain sensitive user data, and the code provides no in-code disclosure, consent gate, redaction, or policy enforcement before transmitting them off-platform.
The example call hard-codes gl: "us" and hl: "en", and the description promotes geographic/language targeting, but the documentation does not state that locale should be chosen based on user preference. This can implicitly steer use toward English/US settings without user opt-in.