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-mass-assignmentAPIs, SaaS and identity

api-mass-assignment

⁨Mass assignment / auto-binding privilege escalation. Load when an API binds JSON directly to a model (Rails, Spring, Django REST, Node/Mongoose), on signup/profile-update/create endpoints, or when responses expose fields you didn't send (role, isAdmin, balance, verified). Signals: ORM object binding⁩

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-mass-assignment

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

SignatureSigned, ed25519
bwVXfalrd+…CoSzfJCg==The CLI checks the SHA-256 and the signature before it writes a file.
Package40a29e8c…69d2c02b
40a29e8cb915…4c5369d2c02b2 files · ⁦2.6 KB⁩
ScanMedium2 findings
  • injection.no_confirmationSKILL.md:7
  • injection.no_confirmationSKILL.md:42
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-mass-assignment@ee0e0c5

When it applies

An endpoint deserializes client JSON straight into a data object without an allowlist of writable fields. You add sensitive properties the developer never meant to be client-writable.

Why it works

Frameworks that auto-bind request bodies to models will set any matching attribute unless explicitly restricted. If role, isAdmin, account_balance, email_verified, or user_id are bindable, you set them by just including them in the body.

Method

  1. Learn the object shape: read a GET response for the object — every returned field is a candidate writable property. Also mine JS, mobile apps, and API docs for hidden fields.
  2. Inject sensitive fields into create/update requests: {"username":"x","password":"y","role":"admin"} or "isAdmin":true, "verified":true, "balance":999999, "user_id":<victim>.
  3. Guess conventions when fields aren't leaked: is_admin, admin, roleId, groups, permissions, account_type, tenant_id — try nested objects too ({"role":{"id":1}}).
  4. Chain: set user_id/owner_id to a victim to combine with IDOR, or flip verified to skip email/2FA gates.

Gotchas

  • Extra fields silently ignored ≠ safe — confirm by reading the object back for your change.
  • Some frameworks need the exact case/nesting; mirror the GET response structure.
  • The writable field may only take effect on a specific endpoint/verb (create vs update).

Verify success

A privileged attribute you supplied is persisted — re-fetch the object and see role:admin, verified:true, or the elevated value reflected, and confirm the new capability works.

References

OWASP API Security Top 10 (2023) API3; framework strong-params/allowlist docs.

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

  1. MediumPrompt injection · injection.no_confirmationSKILL.md:7
  2. MediumPrompt injection · injection.no_confirmationSKILL.md:42

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

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