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/api-bolaAPIs, SaaS and identity

api-bola

⁨Broken Object/Function Level Authorization in REST/JSON APIs (the #1 API risk). Load on any REST API with object ids in paths/bodies (/api/v1/users/123, /orders/{id}), Bearer auth, mobile-app backends, or admin vs user function separation. Signals: predictable ids, verbs that skip re-authorization, ⁩

v2026.10.14-ee0e0c53 installs+3 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/api-bola

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

SignatureSigned, ed25519
hHR3hxSWEQ…gokTDVAw==The CLI checks the SHA-256 and the signature before it writes a file.
Package582dc1dc…682a39c1
582dc1dca3f7…1533682a39c12 files · ⁦2.7 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-bola@ee0e0c5

When it applies

An API exposes objects (BOLA) or privileged functions (BFLA) and enforces authorization weakly. The API version of IDOR — but APIs multiply the surface (many endpoints, verbs, versions, and a mobile client that trusts the server less than the web UI does).

Why it works

APIs are stateless and object-centric; each endpoint must independently check "can this token act on this object/function?". Teams centralize authentication but scatter (or forget) authorization, and hide admin functions in the client instead of the server.

Method

  1. BOLA: with two tokens, request another user's object id on every endpoint & verb; also try guessing/incrementing ids and IDs leaked from list endpoints.
  2. BFLA: take an admin-only call (from JS, mobile, or docs) and replay it with a low-priv token; try method swaps (GET→PUT/DELETE) and hidden verbs the UI never issues.
  3. Version & shadow endpoints: /api/v1/ may lack fixes present in /v2/; /internal/, /debug/, Swagger/OpenAPI docs reveal ungoverned routes.
  4. Automate with Burp Autorize (low-priv token as the "enforcement" session) to flag every request that succeeds when it shouldn't.

Gotchas

  • 200 vs 403 is the tell, but some APIs return 200 with an empty body — diff the content.
  • IDs as UUIDs still leak via list/search endpoints and other objects' relations.
  • Rate-limit and WAF differ per API version — the vuln may only show on an older route.

Verify success

A low-privilege (or cross-tenant) token successfully reads/modifies an object or invokes a function reserved for another user/role.

References

OWASP API Security Top 10 (2023) API1/API5; PortSwigger access-control labs.

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, 2026ee0e0c5582dc1dcSigned–

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