← All bots

Discord application · Evidence

Slade Alerts evidence

Effective September 19, 2026 · Last updated September 19, 2026

Inspect this bot’s workflow, identity and supporting records. Each example distinguishes retrieved messages, observed operation and illustrations.

01Workflow and supporting records

Bot identity and authorized use

Discord bot
Slade Alerts
1515465251280388106
Attached analyst / source author
slade
236729261505904640
Sender channel
#slade-sender
1514078473906290688
Authorized user observed using Send
slade
236729261505904640

The recorded component interaction was accepted for this user. The complete configured allowlist and rejection of unauthorized users have not been inspected.

Verified message records · 2026-09-19

Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

Source, preview and receipt were retrieved read-only through the bot on September 19, 2026. Reply references and component-interaction metadata connect the workflow. The matching destination message was also independently retrieved. Other destinations named in the receipt were not independently checked.

Reconstructed from real Discord messages, with the original text, timestamps and available images, except for explicitly labeled redactions. Layout is simplified; decorative or unavailable media may be omitted. These are website renderings, not screenshots of the Discord client. Source links require access to the channel.

Watch the workflow

Reconstruction from real records · illustrative typing and timing · no live messages

#slade-sender · slade

Illustrative composition of the recorded source message

The saved Discord record proves the sent message, not the original keystrokes.

Step 1 of 6
Inspect all 4 original message records
Analyst sends in the sender channel · #slade-senderReconstruction · real message
slade Discord avatar
slade
well that sucks guess i was to early for that one.
image.png
Message 1521305869814337636 · Author 236729261505904640Open original in Discord ↗
Bot returns the preview and send/edit controls · #slade-senderReconstruction · real message
Slade Alerts Discord avatar
Slade AlertsAPP
Sladq
well that sucks guess i was to early for that one.
Original image attached to Slade Alerts's message

Slade|Powered by Nefarious.Trading

Recorded controls, disabled in this reconstruction.

Message 1521305871278149704 · Author 1515465251280388106Open original in Discord ↗
Bot returns the delivery receipt · #slade-senderReconstruction · real message
Slade Alerts Discord avatar
Slade AlertsAPP
Sladq

Sent with role mention!

✅ Success: `1` `Nefarious` -> `#〔🐶〕slade-alerts` ❌ Failed: `0` ⏱ Duration: `0.275` seconds

Slade|Powered by Nefarious.Trading

Message 1521305876743323728 · Author 1515465251280388106Open original in Discord ↗
Delivered message in the destination channel · #〔🐶〕slade-daytradesReconstruction · real message
Slade Alerts Discord avatar
Slade AlertsAPP
@role
Sladq
well that sucks guess i was to early for that one.
Original image attached to Slade Alerts's message

Slade|Powered by Nefarious.Trading

Message 1521305880555950211 · Author 1515465251280388106Open original in Discord ↗

02Public evidence and removal

These selected examples are public, including any displayed Discord IDs, messages, timestamps, avatars, media and aggregate operational results. Visitors do not need access to the original channel. Credentials, private trading account details and raw message archives are excluded.

Evidence files and deployment copies have no automatic 30-day expiry. Email Business@nefarious.trading with this bot’s name and the relevant example to request correction or removal. Removal must address active pages, downloads, cached media and retained copies under our control. Evidence is not used to train AI models.