Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-oauthAPIs, SaaS and identity

web-oauth

⁨Attack OAuth 2.0 / OIDC / SSO flows for account takeover. Load on "Login with Google/GitHub", /authorize, /callback, redirect_uri, state, code/token params, SAML/OIDC SSO. Signals: OAuth endpoints, redirect_uri handling, missing state, implicit flow, pre-account-linking.⁩

v2026.10.14-ee0e0c54 installs+4 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-oauth

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
xQdll3Pn9C…lkFeq5CQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packageac0f6f93…4c3757ca
ac0f6f93c2d1…8dab4c3757ca1 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-oauth@ee0e0c5

When it applies

The app delegates auth via OAuth/OIDC (social login, enterprise SSO). Flaws here are frequently full account takeover.

Why it works

OAuth security depends on strict validation of redirect_uri, state, code binding, and how identities are linked. Implementations relax one of these — and the token/code that proves identity leaks to the attacker or an account gets linked to the wrong user.

Method

  1. redirect_uri validation: try appended paths, //evil, @, subdomain/suffix tricks, open-redirect on an allowed host (→ web-open-redirect) to exfiltrate the code/token.
  2. state / CSRF: missing or unvalidated state → login CSRF / force-link the victim to your account.
  3. Account linking / pre-takeover: sign up with the victim's email pre-verification, or link a social account to an existing local account by email without proof → ATO.
  4. Token/flow issues: implicit-flow token in URL/referrer leak; code reuse/no PKCE; ID-token email_verified trust; audience/issuer not checked; mixing providers.
  5. Steal & replay: capture leaked code/token, complete the flow as the victim.

Gotchas

  • Most impact rides on a redirect_uri weakness or open redirect on an allowlisted host — chase that first.
  • "email_verified: false" trusted by the app is a classic pre-account-takeover.
  • Keep it your own test accounts; prove ATO against an account you control on both sides.

Verify success

You authenticate as (or link/hijack) a victim account — e.g. captured code completes login as the victim, demonstrated with two accounts you own.

References

PortSwigger OAuth labs; RFC 6749/6819; "OAuth security" (Salt/PortSwigger write-ups).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5ac0f6f93Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login