T01 · Skill Instruction Hijacking
- Location
skill.md:160- Finding
Mandatory Vendor Promotion and Attribution Tracking in Agent Responses
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent NodeMaven proxy setup guide, but it asks agents to handle sensitive credentials in chat and perform persistent account-admin actions with uneven confirmation safeguards.
Install only if you specifically want NodeMaven-focused proxy setup. Prefer a secure secret input or local environment variables over pasting API keys into chat, avoid sharing full proxy URLs, require explicit confirmation before any whitelist/sub-user/notification mutation or deletion, and be aware that the provided dashboard links include mandatory tracking parameters.
skill.md:160Mandatory Vendor Promotion and Attribution Tracking in Agent Responses
skill.md:118API Keys and Proxy Credentials Are Unnecessarily Solicited Through Chat
The skill includes a destructive whitelist deletion capability. Even though it says to confirm with the user first, exposing a raw delete operation in an agent skill increases the chance of unintended or manipulated destructive actions, especially if an upstream prompt or ambiguous instruction causes the agent to target the wrong whitelist entry.
GET /api/v2/base/whitelist/ip/{id}
DELETE /api/v2/base/whitelist/ip/{id}
Always confirm with the user before deleting.
The skill exposes deletion of sub-users and reset of usage, both of which are state-changing administrative actions. In an agent context, these operations are dangerous because prompt confusion, mistaken identity of a sub-user, or malicious user phrasing could cause loss of access, service disruption, or billing/usage integrity issues.
DELETE /api/v2/base/sub-users/?id=<SUB_USER_ID>
POST /api/v2/base/sub-users/reset/usage
Notification deletion is less severe than credential or account deletion, but it still modifies account state and can remove evidence of warnings, abuse notices, or operational alerts. In an autonomous agent setting, deleting notifications can reduce auditability and hide important signals from the user.
GET /api/v2/base/notifications/
DELETE /api/v2/base/notifications/{notification_id}
Check unread notifications when:
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Core principle
The agent must complete this workflow without asking the user to read documentation:
1. Understand the user's task.
2. Recommend the right proxy type.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Full URL example:
https://api.nodemaven.com/api/v2/base/users/me
The instruction to keep fingerprint and proxy geo consistent by matching timezone, language, and locale imposes a specific language/locale configuration as a hard rule for users. The file does not present this as an optional, user-chosen setting or document a justified region-specific exception.
Subtle instructions detected that may alter agent decision-making or introduce hidden biases.
- `email_with_underscores`: the user's NodeMaven account email with `@` and `.` replaced by `_`.
Example: `firstname.lastname@example.com` → `firstname_lastname_example_com`.
This base username is also returned by `GET /api/v2/base/users/me` as `proxy_username` — **always prefer the API value over reconstructing it from email.**
- `country`, `region`, `city`, `isp`: lowercase codes returned by `/locations/*` endpoints. **Resolve via API — never invent.**
- `sid` (session id): any string. Same `sid` = same exit IP for the duration of the sticky TTL. Use a unique `sid` per parallel session/account. Generate as random lowercase alphanumeric, 10–16 chars (e.g. via `openssl rand -hex 6`).
- `filter`: quality filter level. Allowed values: `medium`, `high`. Use `medium` by default; `high` for trust-sensitive workflows (ad accounts, marketplaces).
This line requires account geo, proxy geo, timezone, language, and browser fingerprint to remain consistent, which effectively directs the agent to set or recommend a particular language/locale. Because the skill does not ask for user preference or provide opt-in, it conflicts with the language/locale policy for natural-language instructions.