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

api-grpc

⁨Test gRPC / Protocol Buffers APIs — reflection, method enumeration, authz, and injection. Load on gRPC services (HTTP/2, content-type application/grpc, .proto files, ports like 50051), grpc-web, or "protobuf". Signals: grpc, protobuf, reflection service, ServerReflection.⁩

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-grpc

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

SignatureSigned, ed25519
KcD8tLv7Ff…/RGzR3BA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagec7713f96…47d20b94
c7713f968cc6…67d747d20b941 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/api/api-grpc@ee0e0c5

When it applies

The target exposes gRPC (or grpc-web). Binary framing over HTTP/2 makes it feel opaque, but the same authz/injection bugs apply — and server reflection often hands you the whole API.

Why it works

gRPC methods are RPCs with typed messages; security still lives per-method. Reflection (if on) exposes every service/method, and teams frequently skip auth on internal-looking RPCs or trust the client-generated stubs to enforce access.

Method

  1. Enumerate via reflection: grpcurl -plaintext host:50051 list then list <service> and describe <method>; grpcui for an interactive UI. No reflection? Recover .proto from the client/mobile app or JS (grpc-web).
  2. Call methods directly: grpcurl -d '{"id":123}' host:port pkg.Service/Method — test BOLA/BFLA by calling privileged methods or swapping object ids with a low-priv token.
  3. Auth testing: replay with/without metadata (the gRPC equivalent of headers/tokens); many servers authenticate the connection but not each method.
  4. Injection: message fields feed backends — test SQLi/NoSQLi/command injection in string fields.
  5. grpc-web: it rides HTTP/1.1+base64 — proxy through Burp, decode frames, tamper.

Gotchas

  • Reflection off ≠ safe — extract the schema from clients; then grpcurl with a local .proto.
  • Binary framing hides bugs from scanners; manual method-by-method testing is the win.
  • HTTP/2 + TLS: use -plaintext only when the service is plaintext; otherwise pass certs.

Verify success

Call a method your role shouldn't reach, read/modify another object, or land an injection — proving per-method authz or input handling is broken.

References

grpcurl/grpcui docs; OWASP API Security (2023); "hacking gRPC" 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, 2026ee0e0c5c7713f96Signed–

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