web-rate-limit-bypass
Bypass rate limits and anti-automation to enable brute force, OTP guessing, coupon abuse, and enumeration. Load when an endpoint is throttled (429/"too many attempts"), on login/OTP/reset, or "rate limit". Signals: 429 responses, lockout messages, per-account throttling, OTP/2FA.
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/web-rate-limit-bypassWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package9c5a6d45…746f5582
9c5a6d45494f…6d16746f55821 file · 1.4 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-rate-limit-bypass@ee0e0c5
On this page
When it applies
An endpoint limits attempts (login, OTP/2FA, password reset, coupon, search) and you need more attempts than allowed — to brute force, guess a code, or enumerate. The limit is the only control standing between you and the bug.
Why it works
Rate limits are enforced on a key the attacker can often change or spoof: an IP header, a session, an account id, or a per-endpoint counter. If the key is attacker-controlled or the limit is inconsistent across paths/casing, you reset or dodge the counter.
Method
- Find the key: is the limit per-IP, per-account, per-session, or global? Change it:
- IP spoof headers:
X-Forwarded-For,X-Real-IP,X-Client-IP,X-Originating-IP— rotate values per request; many WAFs/apps trust these. - Session/token: rotate cookies/CSRF tokens; unauthenticated vs authenticated paths.
- IP spoof headers:
- Path/param tricks: case (
/Login), trailing/, added query params, HTTP/2 multiplexing, or a different endpoint that hits the same backend without the limit. - Race the window: fire a burst in parallel before the counter updates (→
web-race-conditions), e.g. many OTP guesses at once. - Automate with Burp Intruder /
ffuf, injecting a rotatingX-Forwarded-Forper request.
Gotchas
- Confirm attempts actually go through (watch for silent drops that return 200 but don't count).
- OTP brute needs the code space small enough (4–6 digits) and no per-account lockout — check both.
- Respect program RoE — brute force is noisy; throttle and stop once the bypass is proven.
Verify success
Attempts continue past the documented limit (no 429), demonstrated by a successful brute/OTP guess or sustained enumeration that the limit should have blocked.
References
OWASP API Security (API4); PortSwigger auth/OTP labs; OWASP WSTG anti-automation.
Files in this version
- SKILL.md2.4 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 | 9c5a6d45 | Signed | – |
More from NoorQureshi
All from this publisherMore in Web and bug bounty
See the category- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
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