ListeningKitdiscordApiInvitesLogin
| Domain | background |
| Kind | endpoint |
| doc_id | — |
| Path | discord.com/api/invites/login |
| Sends | — |
| Reads | message, code |
| Called from | runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1.js:208 app_store_parental_revocation, runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1036.js:1 parse, runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1221.js:2 anonymous, runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder/script1245.js:2 anonymous |
| rea | ev_065e7ad37dcb5911d240f9de7d6e2882220c5a8d7c025d92b46a23de59cf297c |
Seen 1 time(s) in 1 run(s).
| Action | Our step | Times | Status | Took | After step start | Errors |
|---|---|---|---|---|---|---|
| inspect | step 1: goto /login | 1 | 404 | 311 ms | 4280 ms | — |
What it sent and what came back (the newest 1 from our runs)
Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.
runs/inspect/20261028T062914_sourcedandsoldtothehighestbidder, step 1: goto /login: 404, 311 ms
Sent:
{
"query": {
"with_counts": "true",
"with_expiration": "true",
"with_permissions": "true",
"with_games": "true"
},
"body": null
}Answered:
{
"message": "Unknown Invite",
"code": 10006
}What it does
Reads an invite by its code. discord.gg/login reads login as an invite code.
What our machine does with it
Our first goto went to discord.gg/login; this answered 404 Unknown Invite (10006) and the page said Invite Invalid. The login page is discord.com/login.
What can go wrong
404 / 10006 is an invite that doesn't exist or expired; it never means the account is signed out.