Auth0 Android Major Migration

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 9:42 AM UTC
• Version: 1.0.0

Overview

This is a disclosed Auth0 Android v3-to-v4 migration skill, but users should confirm they really want a major upgrade before using it.

Install or invoke this only when you intend an Auth0.Android major migration, not a routine patch bump. Review the planned minSdk, Java, Gradle, AGP, Kotlin, and dependency changes before accepting them, especially because v4 can drop older Android device support and may resolve to a pre-release tag.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection

Findings (10)

Tp4

High

• Category: MCP Tool Poisoning
• Confidence: 99% confidence

Finding

The declared description is about automated migration of an Android Auth0 SDK upgrade, including version detection, prerequisite checks, and targeted code changes. The supplied code does none of that. It is a test utility that loads graders.json from disk, converts grader schema variants into a normalized evaluator format, and exports defineGraders() for test infrastructure. This is a materially different primary purpose, with unrelated behavior and resources, so it is a clear mismatch.

Content

No source excerpt is available for this finding.

Credential Access

High

• Category: Privilege Escalation
• Confidence: 70% confidence

Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 300)May include surrounding context.

md

// v4 — Management client removed; preserve intent, move to a backend
// TODO: Auth0.Android v4 removed the Management API client (UsersAPIClient).
// Expose an endpoint on your own backend (e.g. PATCH /me/metadata) that performs
// this operation. Call it from the app with the user's access token as a Bearer
// token. On the backend, obtain a machine-to-machine token via Client Credentials
// and call the Management API with the minimum required scopes.
// NEVER embed a Management API token in the app.

Credential Access

High

• Category: Privilege Escalation
• Confidence: 70% confidence

Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/process.md (reported line 161)May include surrounding context.

Recommended pattern:

text

App  ──HTTPS (user access token)──▶  Your Backend  ──M2M token──▶  Auth0 Management API

The backend obtains a machine-to-machine token via the Client Credentials grant and calls the Management API with the minimum required scopes.

Credential Access

High

• Category: Privilege Escalation
• Confidence: 70% confidence

Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/security.md (reported line 77)May include surrounding context.

md

### When Auth Flow APIs Change (§7.4 DPoP, scopes)

- Verify the same scopes are still requested — especially `offline_access` for refresh tokens.
- Verify the same audience is still passed for API access tokens.
- Verify the callback URL scheme still matches the Auth0 Dashboard configuration.
- §7.4: moving `useDPoP(context)` to the login builder must not silently drop DPoP — if the app used DPoP before, it must still configure it (now per-request).

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 92% confidence

Finding

The trigger guidance is broad enough to activate on generic requests like 'update my Auth0 Android SDK,' which could cause this major-version migration skill to run when the user only intended a minor or patch bump. In that case, the skill may propose invasive build/toolchain changes such as raising minSdk, Java, Gradle, and AGP versions, increasing the chance of disruptive or unintended modifications.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

The eval prompt explicitly says to use the skill even when the user only says 'update my Auth0 Android SDK,' which is a broad auto-activation trigger that can cause the migration skill to run in situations where the user did not clearly request a major-version migration. In a code-modifying skill, this increases the chance of unintended dependency upgrades, prerequisite changes, and source edits being applied to unrelated maintenance requests.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 75% confidence

Finding

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.

Content

Scanner excerpt · tests/graders.json (reported line 13)May include surrounding context.

json

"type": "judge",
    "description": "Detects current version and resolves/validates the target version dynamically",
    "question": "Does the solution detect the current Auth0.Android version from the project files (build.gradle, build.gradle.kts, libs.versions.toml, gradle.lockfile) and determine the target v4 version by querying GitHub releases (auto-resolving the latest v4 release including pre-releases) or by validating a version passed as an argument?",
    "examples": "PASS: Reads build.gradle.kts to find '3.19.0', then queries the GitHub releases API and resolves the latest v4 tag (e.g. 4.0.0-beta.1).\nPASS: Validates a user-provided version argument as a real published v4 tag that is not a downgrade before using it.\nFAIL: Assumes a target version without checking releases or validating the argument.\nFAIL: Skips version detection entirely.",
    "framework": "android"
  },
  {

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 75% confidence

Finding

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.

Content

Scanner excerpt · tests/graders.json (reported line 27)May include surrounding context.

json

"type": "judge",
    "description": "Detects current version and resolves/validates the target version dynamically",
    "question": "Does the solution detect the current Auth0.Android version from the project files (build.gradle, build.gradle.kts, libs.versions.toml, gradle.lockfile) and determine the target v4 version by querying GitHub releases (auto-resolving the latest v4 release including pre-releases) or by validating a version passed as an argument?",
    "examples": "PASS: Reads build.gradle.kts to find '3.19.0', then queries the GitHub releases API and resolves the latest v4 tag (e.g. 4.0.0-beta.1).\nPASS: Validates a user-provided version argument as a real published v4 tag that is not a downgrade before using it.\nFAIL: Assumes a target version without checking releases or validating the argument.\nFAIL: Skips version detection entirely.",
    "framework": "android"
  },
  {

Unpinned Dependencies

Low

• Category: Supply Chain
• Confidence: 40% confidence

Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · tests/package.json (reported line 13)May include surrounding context.

json

"eval:grade-only": "node run-evals.mjs --grade-only"
  },
  "dependencies": {
    "execa": "^9.0.0",
    "ora": "^8.0.0"
  }
}

Unpinned Dependencies

Low

• Category: Supply Chain
• Confidence: 40% confidence

Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · tests/package.json (reported line 14)May include surrounding context.

json

},
  "dependencies": {
    "execa": "^9.0.0",
    "ora": "^8.0.0"
  }
}

Static analysis

No suspicious patterns detected.