Skip to content

ajtazer/heckit / skills/cloud-container/okta-attack

okta-attack

Flagged

Okta-as-IdP red-team attack chain — tenant discovery, user enumeration (multiple vectors), authentication flow analysis (factors enumeration, push-notification fatigue, SMS bypass), password spray with lockout discipline, Okta-specific phishing primitives (kits, FastPass abuse, OIDC redirect_uri tampering), MFA enumeration, post-compromise admin API surface. Many enterprise orgs use Okta instead of (or alongside) Entra ID. Distinct endpoints, distinct rate-limiting, distinct factor flows. Use when recon shows `<tenant>.okta.com`, `<tenant>.okta-emea.com`, `<tenant>.oktapreview.com`, or autodiscover-style records pointing at Okta IdP.

Security report

Flagged

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
f82481acf60da8b636a5af97df17d3c46f0939aa
Content hash
3e513c69dc45c9f0a1cab920420f4ad8b40d969e392fb6694c3f315f61f4f40e
Scanned
2026-11-17
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
1 open critical or high finding.
Verification expires
Not applicable

Findings (1 high)

  • highCMD-REMOTE-PIPE-SHELLSKILL.md:200

    A script is downloaded and run in one step, so whatever the server returns at that moment is executed without review.

    curl -sk "https://<tenant>.okta.com/.well-known/openid-configuration" | python3 -m json.tool

    Suggested fix: Download the script, check it (and its checksum or signature), then run the saved copy. Prefer a package manager.

    Report as false positive

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall