PlatformsDiscordBackground

discordApiUsersMeMfaWebauthnCredentials

Domainbackground
Kindendpoint
doc_id—
Pathdiscord.com/api/users/@me/mfa/webauthn/credentials
Sends—
Reads—
Called fromruns/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
reaev_065e7ad37dcb5911d240f9de7d6e2882220c5a8d7c025d92b46a23de59cf297c

Seen 6 time(s) in 4 run(s).

ActionOur stepTimesStatusTookAfter step startErrors
inspectstep 1: goto /channels/@me/<id>1200357 ms11797 ms—
inspectstep 5: click e401200392 ms12886 ms—
inspectstep 9: goto /channels/@me1200453 ms9529 ms—
inspectstep 25: goto /channels/@me1200359 ms8642 ms—
inspectstep 1: goto /login1200366 ms18469 ms—
inspectstep 2: snapshot1200479 ms51717 ms—

What it sent and what came back (the newest 3 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/20261030T222341_sourcedandsoldtothehighestbidder, step 2: snapshot: 200, 479 ms

Sent:

null

Answered:

[]

runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 200, 366 ms

Sent:

null

Answered:

[]

runs/inspect/20261028T065202_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me/<id>: 200, 357 ms

Sent:

null

Answered:

[]

What it does

Lists the account's security keys and passkeys.

What our machine does with it

Nothing in log-cli waits for it or reads it. It is part of what Discord's client loads around the page; a watch or a send never depends on it.

What can go wrong

A failure only hides the security-key list in settings.