Dangling B2 bucket reference — ShellBags Explorer download link

reference — ShellBags Explorer download link

**Summary**
The direct download link for ShellBags Explorer via Backblaze B2
appears to point to a bucket that no longer exists:

`https://f001.backblazeb2.com/file/EricZimmermanTools/ShellBagsExplorer.zip`

Requesting this URL returns:

​```json
{
"code": "not_found",
"message": "Bucket with such name does not exist.",
"status": 404
}
​```

**Why this matters**
When testing (without completing registration or entering real
payment details), the bucket name `EricZimmermanTools` did not
trigger a name-conflict error during bucket creation on B2 — the
flow only stopped at the billing step. This suggests the name may
currently be unclaimed and could potentially be re-registered by
an unrelated third party.

If that happens, any legacy link, script, or documentation still
pointing to this bucket could end up serving content from an
unauthorized source instead of the original tool — a supply-chain
risk given this toolset's use in forensic investigations.

**What I've done**
I've already submitted a responsible disclosure report to
Backblaze's security team (`security@backblaze.com`) with full
technical details and screenshots. Happy to share that report here
too if useful.

**Suggested action**
Worth confirming whether current official download links still
rely on this bucket, and updating any references if they're
outdated (e.g. pointing users to the GitHub Releases page instead).

Thanks for all the great tools — just wanted to flag this in case
it's relevant.

Search the repository and official download references for ShellBags Explorer, starting with the Backblaze B2 URL in the issue. Verify whether current links still use that bucket and compare them with the GitHub Releases page; done means outdated references are identified and updated or confirmed as current.

Written by the indexing model from the issue text.