events · last 24 h
118
across 14 separate hours of the last 24.
live on telegram
@umbra_checker_bot
/
24/7
Send a Target.
Get a Checker.
One message in Telegram — the login page and a test account. From there it runs on its own: audit, build, then an adversary whose only job is to break it. What arrives in your chat is a standalone checker, tested and proven working before you pay a penny.
- Median 1h44mmost builds land inside 3 hours
- Built and testedyou pay after it works
- $5 flatevery target · first one free
- 24/7no queue, no waiting days
authorised testing only · accounts and systems you own or may test
-
01requestqueued
-
02auditqueued
-
03approvequeued
-
04buildqueued
-
05break itqueued
-
06deliverqueued
gates 0/4
arms 0/8
false pos 0
median 104 min
01 — the flow
Six stages. One message.
Everything runs in Telegram — nothing to install, nothing to learn. You send one thing; the machine does the rest and tells you where it is. The median build lands 1h44m after the request, and a hard target can run longer: you watch it live either way.
-
01
You send the target
A login URL and one test account. That is the whole intake. The credential is encrypted on arrival and deleted the moment the audit has used it.
-
02
It gets audited
Probed for real: what kind of login it is, whether a browserless checker can actually be built. A non-answer is never treated as a “no” — and if it can't be checked, you're told plainly.
-
03
You decide
Buildable? You get the offer and press Build it. Nothing is built before you tap. Your first checker is free; after that it's $5, the same price for every target.
-
04
It builds & tests
The checker is written and run against the live target — a real account must HIT, a junk one must MISS, and a throttle must never be scored as a credential answer.
-
05
An adversary breaks it
A separate pass that did not write the code tries to destroy it: rate-limits, ghosts, hostile replies, a mid-run kill, an offline network. Anything it breaks goes back and is re-proven.
-
06
It's delivered
Zipped, hashed, sent in the chat with a HOWTO. It runs entirely on your machine: your combos, your proxies, your console. The file never talks to us.
02 — the deliverable
A file. Not a service.
What lands in the chat is one standalone program, built for one login page. No account on our side, no licence check, no callback, no telemetry. The numbers on this page come from our own runs — the file you get reports to nobody. You own the copy you were given.
- Written for that login — form shape, CSRF handling and JSON body come from your target's audit, with the markers that separate a real HIT from a WAF page. Not a generic scraper pointed at a URL.
- Four files — the checker, named after your target, plus combo.txt, proxy.txt and HOWTO.md as commented templates. The manifest and our working notes stay on our side.
- Never a fake MISS — HIT, MISS, and a separate bucket for “no answer”: retry, re-queued, exhausted. A 429, a challenge page or a burned exit is never scored as a bad password, and the summary prints every bucket on its own line.
- One dependency, self-installing — the first run fetches curl_cffi; no requirements file, no pip line to get wrong. The HOWTO is written for someone who has never run a script: the exact prompts, what each verdict means, what a 429 is.
- Resume — Ctrl-C or a closed terminal: it continues from the last scored combo without double-counting.
- Capture — where the target exposes it, a HIT carries the account's own fields, not just “password matched”.
$ unzip umbra-lab_v1.zip acme_umbra_v1.py combo.txt proxy.txt HOWTO.md $ python3 acme_umbra_v1.py ┌──────────────────────────────────────────┐ │ UMBRA LAB CHECKER v1 │ │ for acme.example /account/login │ │ standalone · no phone-home · no limits │ │ hits saved next to the script │ └──────────────────────────────────────────┘ Combo file combo.txt Proxy menu [1] use proxy.txt [2] proxyless Shape ROTATING Threads [20] 🎯 HIT: j•••@gmail.com | profile 7/9 captured ✅ DONE — 4,812 checked in 11m 40s · 412 CPM ✅ 3 hits │ ❌ 4,806 misses ⚠️ 2 retry │ ↻ 0 requeued │ ✕ 0 exhausted → acme_hits_20261103.txt (same folder)
zip sha256 verified4 filesno manifest · no callback
03 — telemetry
It doesn't sleep. Here's the evidence.
Counted from the live order book when this page loads — requests, deliveries, and the time each one took. snapshot —
requests · since launch
326
2 in the last 24 hours · 5 the day before.
median · request → delivered
104min
p90 334 min · 75% inside 3 hours.
checkers delivered
135
3 in the last 24 hours. Unbeatable orders close with no charge.
loading…
last 48 h · newest first · target names only
04 — the library
What has already been built.
target
domain
waf
seen
One price, every target — $5, flat. A shop with no wall and a bank-grade WAF cost the same: no difficulty pricing, no rush fee, and no reselling someone else's list. The first checker on a new account is free.
05 — managed runs
Run it at scale.
A 24-hour run answers the whole list at once, not one account at a time. If the target is already in the library, it has been tested — message us and we book the day. If it is not listed, send it to the bot with one test account: the fastest way to learn whether a checker can be built. When the bot says buildable, message us and we take the run. You don't drive anything: the hits arrive.
how a run is booked
- 01
Check the library first
youSearch the index. If the target is listed, that login is already tested and the path is known — say the word and the run can be booked straight away. That is the fast lane.
- 02
Not listed? Send it to the bot
youOpen @umbra_checker_bot and send the login URL plus one test account. It is faster and simpler than asking us by hand: same request, same audit, and you get the answer in the chat. If it can't be checked, you're told and nothing is charged.
- 03
Bot says buildable? Message us
youBring us that verdict — the target and the bot's answer. That one message is what turns a target into a booked 24-hour run: we confirm the date and quote it.
- 04
Pick your 24 hours
youSame message as step 03 — you name the window, we confirm the date and quote it. One run at a time, so the day you book is the day you get.
- 05
The combolist
youBring your own, or we supply one — agreed when you book. Either way the format is settled before the day.
- 06
Exits & servers
usOurs. Exits sized to the target's wall and the volume, workers provisioned for the run, monitored throughout.
- 07
The run
us24 hours, continuous. It starts on 24 workers — and on a good day, when servers free up, it scales up to 100. Whatever capacity we get, it holds for the whole window.
- 08
Hits live, then handover
usEvery hit reaches your Telegram bot as it lands. At the end you get a TXT of all hits plus the capture report.
you bring
- the target
- one test account (for the build check)
- your combolist — optional
- the 24-hour window you want
we bring
- the audit and the build
- exits / proxies sized to the target
- servers, workers and monitoring
- hit delivery + the final TXT
how it's priced
Priced per run, quoted before we book — it depends on the wall, the volume and whether we supply the combos. Nothing is payable until the date is agreed.
A run only starts on a target that passed the build check. If the door closes mid-run, the run pauses and you're told — we don't manufacture hits.
Got a target and a list? Send the target to the bot first — if it builds, we'll book the day.
06 — pricing
Five dollars. Every target.
No tiers, no seats, no subscription, no per-hit upsell. The price is the price whether the target is a shop login or a fight.
01 first checker
Free
one per new customer. Same build, same gates, same delivery — not a demo.
Claim it
pay after it's built
02 every checker after
$5 / target
- audited, built, tested, independently checked
- you only pay once the file is packaged and waiting
- BTC · LTC one address per order
- held 6 h while you pay — then the slot frees
03 refer 3
+1 free
send three people who actually build — you get another free checker. Tell @intimewewin who you sent.
Message ussame price for every target · 24/7 · nothing charged on a target we can't check
07 — the lab
Where the work happens. Open a door.
Umbra Lab isn't a script farm — it's a lab with a pipeline. The buildable targets post publicly, and the whole thing is wired to the same bot.
the bot
@umbra_checker_bot
The front door. Send a URL and a test account; everything else is a button.
open telegram → the lab feedThe Lab · Blackboard
Every new target that clears audit posts here first — the buildable list, in public, as it happens. Private invite — the bot posts, the list is live.
follow the feed → get in touch@intimewewin
Not sure whether a target can be checked, or want one run at scale? Message me directly — same chat, same answer.
open telegram →08 — questions
The honest answers.
What exactly do I get?
A standalone checker built for the target you sent, zipped with a HOWTO and a manifest. You run it on your own machine with your own combos and proxies. No account on our side, no licence check, no callback.
Do I need to know how to code?
No. You need Telegram and two text files. The HOWTO covers the run, the verdicts, and what a rate-limit looks like.
What if the target can't be checked?
The audit says so before anything is built, and nothing is charged. If it dies later — an account gets locked, or a wall holds — the order closes cleanly and you're told why. We would rather kill an order than hand you a false-negative machine.
How long does it take?
Most targets finish inside one sitting — measured across the live system, the median from request to delivered is 104 minutes, with a long tail for targets that fight. Simple logins move much faster; walls can take hours.
Is my test account safe?
It's encrypted the moment it arrives, used only for this order, and deleted once the audit is done. Messages you send are cleared after being read, and the delivered file contains no credential of yours.
Why only one order at a time?
Because each order gets a real slot and a real worker rather than being queued behind a hundred others. Finish or cancel one, and the next opens immediately.
Do I pay before or after?
After. Umbra Lab builds, tests, verifies and packages first — then asks. You see “ready — pay to unlock” only when the file actually exists. BTC or LTC, one address per order.
Is it the same price for a hard target?
Yes. $5, flat. The first checker on a new account is free. There is no “hard target” surcharge and no rush fee — the queue is the queue.
ready when you are
Send one target.
See what comes back.
First checker free. No card, no account, no install — just the chat.
Open @umbra_checker_bot
scan on mobile
scan on mobile