Nefarious Backup

Intent relevance

Message Content lets the bot serialize ordinary channel history, embeds and supported attachments into its archive and create backup copies. The deployed command check restricts operator controls to configured user IDs.

The deployed script, non-secret configuration, saved state and snapshot manifests were inspected read-only. The latest recorded snapshot is historical; this inspection did not run a backup, restore, mirror or Discord command.

Bot identity and authorized use

Bot: Nefarious Backup · 1511899722393063544

Attached analyst: Not applicable — operator-controlled backup

The deployed user-ID allowlist authorizes enickfutures (223573186711650304), teever (262674782171037698) and johnnylixf (196479731737034752). The command check requires one of these IDs; Discord Administrator permission alone does not pass it.

Recorded backup output and operator workflow

Inspected 2026-09-19T19:55:36.200853+00:00 · Historical capture

Saved snapshots

4 / 4

Latest snapshot manifest

2026-09-06T05:30:40.510229+00:00

Messages reported by latest manifest

489,682

Channels reported by latest manifest

178

Message archive

SQLite archive exists; message bodies excluded from this public example

Server Members intent

Disabled in the inspected configuration

1. Authorized operator controls

An allowlisted operator can type ?backup status or ?backup list. This is a code-backed command example; no command was sent during inspection. The status handler returns an embed with saved snapshot counts, mirror progress and archive status. Internal paths and private destination details are omitted here.

2. Bot reads and archives channel history

The deployed serializer keeps message content, embeds, author display data and supported image metadata. The archive uses message IDs to resume collection. This is why Message Content is needed.

3. Bot saves snapshot output

The actual retained manifest dated 2026-09-06T05:30:40.510229+00:00 reports 489,682 messages across 178 channels. Four snapshot entries were found. This verifies retained output, not a new backup run.

4. Bot can mirror and restore

The deployed mirror reads archived entries and reposts supported content using webhooks with mentions disabled. Restore can purge and repost destination content; no restore was executed or independently demonstrated in this inspection.

The latest recorded snapshot is September 6, 2026. A configured daily schedule does not prove later runs succeeded. The retained manifest has no completion flag; completeness and successful restore were not independently verified. Snapshot-count rotation does not expire the underlying message archive.