Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Amazon Ads helper that uses user-provided credentials to fetch account data, with some overstated documentation but no hidden persistence or unrelated data handling.
Install only if you are comfortable giving the skill access to an Amazon Ads credential file. Use a credential limited to the advertiser accounts and permissions you intend, store the credential file carefully, and treat --out exports as sensitive campaign/account data.
The skill description overstates its behavior and omits important side effects, including writing fetched campaign data to a local file via --out. This mismatch can mislead users and automated policy systems into granting trust or permissions under false assumptions, increasing the risk of unintended data exposure or unsafe execution in environments handling advertiser account data.
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
Referenced artifact was not completely inspected
node scripts/ads.js --profiles
The skill declares executable behavior that uses environment variables and network access, but it does not declare any tool scope such as permissions or allowed-tools. This weakens policy enforcement and reviewability, because an agent may invoke capabilities to read secrets and contact external Amazon endpoints without explicit authorization in the manifest.
The script reads a credentials file from a path in AMAZON_ADS_PATH or a local default file and then parses secrets from it, but there is no visible warning, prompt, or explanatory comment disclosing that sensitive advertising API credentials will be accessed. Because this is a code file handling credentials, some user-facing or documented disclosure is expected under the rule when no other warning is present in the file.
The token request sends refresh_token, client_id, and client_secret to Amazon over HTTP(S), and subsequent API calls transmit authenticated account data, but the script provides no user-facing disclosure that sensitive data will be sent to external Amazon endpoints. The usage header describes commands only and does not warn about outbound authenticated requests.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function getAccessToken() {
const creds = getCreds();
const res = await fetch('https://api.amazon.com/auth/o2/token', {
method: 'POST',
headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
body: new URLSearchParams({
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function getAccessToken() {
const creds = getCreds();
const res = await fetch('https://api.amazon.com/auth/o2/token', {
method: 'POST',
headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
body: new URLSearchParams({
When --out is supplied, the script writes fetched campaign data to disk, but there is no prior warning in comments, help text, or runtime messaging that local files may be created containing account information. The only message appears after the write has already occurred.
Detected: suspicious.env_credential_access, suspicious.exposed_secret_literal