Discord application · Evidence
Dingus 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
- Dingus Alerts
1537411077900603404 - Attached analyst / source author
- Dingus
1354113768476639246 - Sender channel
- #dingus-sender
1537410176930291712 - Authorized user observed using Send
- Dingus
1354113768476639246
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
#dingus-sender · Dingus
Illustrative composition of the recorded source message
The saved Discord record proves the sent message, not the original keystrokes.
Inspect all 4 original message records
Dingus
babajaga2ghz|Powered by Nefarious.Trading
Recorded controls, disabled in this reconstruction.
DingusSent with role mention!
babajaga2ghz|Powered by Nefarious.Trading
Dingusbabajaga2ghz|Powered by Nefarious.Trading
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.