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-grpcWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec7713f96…47d20b94
c7713f968cc6…67d747d20b941 file · 1.3 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-grpc@ee0e0c5
On this page
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
- Enumerate via reflection:
grpcurl -plaintext host:50051 listthenlist <service>anddescribe <method>;grpcuifor an interactive UI. No reflection? Recover.protofrom the client/mobile app or JS (grpc-web). - 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. - Auth testing: replay with/without metadata (the gRPC equivalent of headers/tokens); many servers authenticate the connection but not each method.
- Injection: message fields feed backends — test SQLi/NoSQLi/command injection in string fields.
- grpc-web: it rides HTTP/1.1+base64 — proxy through Burp, decode frames, tamper.
Gotchas
- Reflection off ≠ safe — extract the schema from clients; then
grpcurlwith a local.proto. - Binary framing hides bugs from scanners; manual method-by-method testing is the win.
- HTTP/2 + TLS: use
-plaintextonly 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
- SKILL.md2.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
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.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | c7713f96 | Signed | – |
More from NoorQureshi
All from this publisherMore in APIs, SaaS and identity
See the category- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login