navan-install-auth
Pass
Audited by Gen Agent Trust Hub on Sep 12, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONREMOTE_CODE_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [DATA_EXPOSURE_AND_EXFILTRATION]: The skill implements secure credential management practices. It instructs users to store sensitive OAuth 2.0 credentials in a local
.envfile and provides specific commands to add this file to.gitignoreto prevent accidental credential exposure in version control systems. - [EXTERNAL_DOWNLOADS]: The skill facilitates the installation of standard, widely-used libraries from official registries, including
dotenvfor Node.js andrequestsandpython-dotenvfor Python. These are established tools for handling environment variables and HTTP operations. - [REMOTE_CODE_EXECUTION]: An example command demonstrates using
curlto fetch a token from Navan's API and piping the result topython3for JSON parsing. As the target is the official API of a well-known service (api.navan.com), this is considered a safe integration pattern for verification purposes. - [INDIRECT_PROMPT_INJECTION]: The skill has a surface for indirect prompt injection because it ingests data from the Navan API and processes user-supplied credentials. However, the logic applied to this data (confirming token acquisition and checking record counts) does not present an exploitable capability chain.
- Ingestion points: Local
.envfile configuration and remote responses from the Navan REST API. - Boundary markers: None explicitly defined in the code snippets, relying on standard JSON deserialization.
- Capability inventory: Includes network requests (
fetch,requests,curl), file system writes (for.envand.gitignore), and package management (npm,pip). - Sanitization: Uses standard platform libraries for environment variable parsing and HTTP response handling.
Audit Metadata