Aug 01, 2026, 08:56 PM
I’m dropping this for people who already think about what a picture still holds after you think you’re done with it.
[COLOR=rgb(255, 0, 0)]This is free, full source included. I’m not selling access, You get a script, you run it locally, you read it if you want. What happens on your machine stays a problem between you and your own OpSec.[/COLOR]
Who this is for
Dark-web side of life is full of screenshots: panels, chats, wallets, tickets, errors, file managers,Soft blur and "I cropped it in a random editor" fail more often than people admit. Text shape stays. Metadata stays. A second copy of the original stays on disk. Someone .. or some model .. gets another pass at what you thought was gone.
If that problem is real for you, this is aimed at that problem. If soft blur was always enough, you can ignore this post.
https://bf.st/attachments/2948/
What it is
Local tool. Tray icon after unlock. You either:
grab a region of the screen, or
open an image from disk
Then you mark areas by hand and apply tools. When you export, the file is rebuilt from pixel data so the usual embedded metadata does not ride along. Optional stamp of your nickname + PGP fingerprint so a file is harder to casually pass off as someone else’s wor
Password and encrypted config
On first run you set:
nickname
PGP fingerprint (or whatever long id you use as a mark)
save folder for exports
password (with confirm)
https://bf.st/attachments/2949/
That identity is not left as plain text on disk. It is written into a sealed local config under your home directory. The password is not stored. Every time you start the tool you unlock that config into memory for that process only. Close it, and the sensitive fields are not meant to sit decrypted on disk waiting for the next casual look at the folder.
Forget the password and there is no recovery email. You delete the local config directory and set up again. That is intentional: no cloud reset, no backdoor.
Settings changes later also require the same password. Same idea - if someone is sitting at your unlocked session, they still should not casually edit your watermark identity without that secret.
How it runs (CPU / RAM)
All heavy pixel work is CPU-side, inside the process (Pillow / plain Python). There is no GPU path and no native accelerator stack. That keeps the dependency list small and behaviour predictable on a normal machine.
So: small selections stay quick; large selections can hitch for a few milliseconds while the filter walks the region. That is expected. This is not Photoshop and it is not trying to be realtime video. The priority is destroying or replacing what you marked, not maximising frames per second.
RAM: the open image, undo history, and live edits stay in memory until you save or close. That is deliberate .. less junk written to disk mid work. It also means a very large screenshot plus a deep undo stack will use more RAM. Panic and closing without save drop those buffers for the open editors. Exports you already wrote to disk are separate files on disk.. they are not "held only in RAM."
Panic button
There is a red PANIC control in the editor, and the same action from the tray menu.
When you hit it:
every open editor closes without saving
undo / redo and image buffers for those windows are dropped from memory
session identity is cleared from memory
the tool locks again and asks for the password before you continue
Use it when focus is gone mid edit .. someone walks in, you need the screen clean of half finished work, you do not want an unsaved frame sitting in RAM on an unlocked session. Panic does not delete exports you already wrote to disk. It stops the live work and relocks the tool.
Tools (what they are for)
You pick a rectangle. Nothing auto detects "secrets" for you on purpose.
Crop - cut the frame down
Blur - soft or harsh
NULLBURN - heavy destroy path: displace / scramble / noise, then full random overwrite of the selection so the old samples in that box are not sitting in the buffer anymore
Mask - solid fill (pick a colour or sample the background)
Scramble - shuffle pixels in the box
RGB - break structure in the channels
Mesh - geometric overlay that fights easy OCR-style reading
Spoof - paint fake text that tries to sit on the local background (still verify by eye)
Arrow / Text / Zoom
Invert - reversible, do not treat it as protection
Eyedropper (PICK) - click a pixel, lock that exact colour for Mask / Spoof / Mesh / Text
Also on the chrome:
Undo / Redo
Branding on/off + opacity for the nickname/fingerprint stamp
Hold preview - press to see the export look (including branding), release to return
Discard - close the editor with confirm, no save
Save - full export pipeline (below)
Batch watermark from the tray if you only need to brand a folder of images and ofcourse metada will be deleted for the all imges in the folder
Export pipeline
Short report of metadata that was on the source, and a clear note that the export is rebuilt stripped
If the image was opened from disk, optional wipe original after successful export (default off)
Choose format: PNG / JPEG / WEBP / BMP
Write under your save path with a random filename
If wipe is enabled, you confirm twice. The tool overwrites the source file bytes, truncates, renames, deletes that path. Best-effort. It does not invent guarantees about SSD wear-leveling, backups, or other copies. The export path is never the wipe target.
Edits stay in RAM until you save. Undo history is in RAM. That is why Panic and closing without save matter.
Why "harder to recover" is the point
Soft blur keeps structure. A determined eye - or automated help - can still lean on edges and spacing. Metadata is a free second channel. The original file next to your “clean” export is the real leak.
This tool is built so that, for the region you marked, you can replace or destroy what was there instead of only smearing it, then export without the usual baggage, and optionally remove the source file you imported. That does not make you invincible. It raises the cost of reading that region back from this file. Another copy you already sent is out of scope. Bad judgment is out of scope.
Stack / install
Python. tkinter. Pillow. mss. pystray. Fully offline
requirements.txt is short. README is install steps only (Linux first: Debian / Ubuntu / Kali, then Windows / macOS), including practical notes
Limits - read this once before you rely on it
Not a lab proof erase guarantee. Optional wipe of an imported original overwrites and deletes that path as best effort. SSDs with wear-leveling,cloud sync, recycle bins, and copies you already made can still hold data. Do not treat wipe as magic against a forensic lab.
Not automatic intelligence. Nothing scans the image to decide what is sensitive for you. You mark the region. That is intentional - fewer surprises, fewer false trusts.
Panic is for the live session, not history on disk. Panic closes open editors without saving, clears buffers, and locks the password gate again. Files you already exported stay where you saved them. If those need to go, that is a separate decision.
Weak tools stay weak on purpose in the list. Invert is reversible. Soft blur still leaves structure. Use them for mild cover only. When a region must not come back easy - to an eye or to automated recovery - prefer NULLBURN or a solid Mask, then check the export yourself.
Another copy is out of scope. If the same frame already left your machine, this tool cannot recall it. It only improves what you do with the copy you still control.
CPU, not GPU. Large regions can take a short moment. That is the cost of staying a plain offline script with no heavy runtime.
I built this as a small offline gift for people who live with screenshots as evidence risk. Use it, read it, or ignore it. If it helps .. good
Support / Tips [COLOR=rgb(226, 80, 65)](Optional)[/COLOR]
This project is completely free and open-source. If this tool saves you time, helps protect your workflow, or if you simply appreciate the effort and want to support future tools and development, tips are always appreciated (never expected, but always welcome):
[COLOR=rgb(251, 160, 38)](XMR)[/COLOR]: [COLOR=rgb(250, 197, 28)][ 89QRPNnqCgm6aanvjhby71U2usNS4TfZhBEa72KdcmwnXfi1cHTV5exfozeLLrqpG3YkfjpQefPcfEeUTzuhmcJH4Mi5b7E ][/COLOR]
Files attached: Script,README,Requirements.txt
"Rename the files after download"
09FD-SHIELD.py
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/b61e25465c50652f/a21c9d11a1d59be7.py[/URL]
README.md
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/987c315f7a06b3d3/cb8dc75c6b80bc.md[/URL]
requirements.txt
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/4f064bc64aeb69/f511a95a5c0de85f.txt[/URL]
[COLOR=rgb(255, 0, 0)]This is free, full source included. I’m not selling access, You get a script, you run it locally, you read it if you want. What happens on your machine stays a problem between you and your own OpSec.[/COLOR]
Who this is for
Dark-web side of life is full of screenshots: panels, chats, wallets, tickets, errors, file managers,Soft blur and "I cropped it in a random editor" fail more often than people admit. Text shape stays. Metadata stays. A second copy of the original stays on disk. Someone .. or some model .. gets another pass at what you thought was gone.
If that problem is real for you, this is aimed at that problem. If soft blur was always enough, you can ignore this post.
https://bf.st/attachments/2948/
What it is
Local tool. Tray icon after unlock. You either:
grab a region of the screen, or
open an image from disk
Then you mark areas by hand and apply tools. When you export, the file is rebuilt from pixel data so the usual embedded metadata does not ride along. Optional stamp of your nickname + PGP fingerprint so a file is harder to casually pass off as someone else’s wor
Password and encrypted config
On first run you set:
nickname
PGP fingerprint (or whatever long id you use as a mark)
save folder for exports
password (with confirm)
https://bf.st/attachments/2949/
That identity is not left as plain text on disk. It is written into a sealed local config under your home directory. The password is not stored. Every time you start the tool you unlock that config into memory for that process only. Close it, and the sensitive fields are not meant to sit decrypted on disk waiting for the next casual look at the folder.
Forget the password and there is no recovery email. You delete the local config directory and set up again. That is intentional: no cloud reset, no backdoor.
Settings changes later also require the same password. Same idea - if someone is sitting at your unlocked session, they still should not casually edit your watermark identity without that secret.
How it runs (CPU / RAM)
All heavy pixel work is CPU-side, inside the process (Pillow / plain Python). There is no GPU path and no native accelerator stack. That keeps the dependency list small and behaviour predictable on a normal machine.
So: small selections stay quick; large selections can hitch for a few milliseconds while the filter walks the region. That is expected. This is not Photoshop and it is not trying to be realtime video. The priority is destroying or replacing what you marked, not maximising frames per second.
RAM: the open image, undo history, and live edits stay in memory until you save or close. That is deliberate .. less junk written to disk mid work. It also means a very large screenshot plus a deep undo stack will use more RAM. Panic and closing without save drop those buffers for the open editors. Exports you already wrote to disk are separate files on disk.. they are not "held only in RAM."
Panic button
There is a red PANIC control in the editor, and the same action from the tray menu.
When you hit it:
every open editor closes without saving
undo / redo and image buffers for those windows are dropped from memory
session identity is cleared from memory
the tool locks again and asks for the password before you continue
Use it when focus is gone mid edit .. someone walks in, you need the screen clean of half finished work, you do not want an unsaved frame sitting in RAM on an unlocked session. Panic does not delete exports you already wrote to disk. It stops the live work and relocks the tool.
Tools (what they are for)
You pick a rectangle. Nothing auto detects "secrets" for you on purpose.
Crop - cut the frame down
Blur - soft or harsh
NULLBURN - heavy destroy path: displace / scramble / noise, then full random overwrite of the selection so the old samples in that box are not sitting in the buffer anymore
Mask - solid fill (pick a colour or sample the background)
Scramble - shuffle pixels in the box
RGB - break structure in the channels
Mesh - geometric overlay that fights easy OCR-style reading
Spoof - paint fake text that tries to sit on the local background (still verify by eye)
Arrow / Text / Zoom
Invert - reversible, do not treat it as protection
Eyedropper (PICK) - click a pixel, lock that exact colour for Mask / Spoof / Mesh / Text
Also on the chrome:
Undo / Redo
Branding on/off + opacity for the nickname/fingerprint stamp
Hold preview - press to see the export look (including branding), release to return
Discard - close the editor with confirm, no save
Save - full export pipeline (below)
Batch watermark from the tray if you only need to brand a folder of images and ofcourse metada will be deleted for the all imges in the folder
Export pipeline
Short report of metadata that was on the source, and a clear note that the export is rebuilt stripped
If the image was opened from disk, optional wipe original after successful export (default off)
Choose format: PNG / JPEG / WEBP / BMP
Write under your save path with a random filename
If wipe is enabled, you confirm twice. The tool overwrites the source file bytes, truncates, renames, deletes that path. Best-effort. It does not invent guarantees about SSD wear-leveling, backups, or other copies. The export path is never the wipe target.
Edits stay in RAM until you save. Undo history is in RAM. That is why Panic and closing without save matter.
Why "harder to recover" is the point
Soft blur keeps structure. A determined eye - or automated help - can still lean on edges and spacing. Metadata is a free second channel. The original file next to your “clean” export is the real leak.
This tool is built so that, for the region you marked, you can replace or destroy what was there instead of only smearing it, then export without the usual baggage, and optionally remove the source file you imported. That does not make you invincible. It raises the cost of reading that region back from this file. Another copy you already sent is out of scope. Bad judgment is out of scope.
Stack / install
Python. tkinter. Pillow. mss. pystray. Fully offline
requirements.txt is short. README is install steps only (Linux first: Debian / Ubuntu / Kali, then Windows / macOS), including practical notes
Limits - read this once before you rely on it
Not a lab proof erase guarantee. Optional wipe of an imported original overwrites and deletes that path as best effort. SSDs with wear-leveling,cloud sync, recycle bins, and copies you already made can still hold data. Do not treat wipe as magic against a forensic lab.
Not automatic intelligence. Nothing scans the image to decide what is sensitive for you. You mark the region. That is intentional - fewer surprises, fewer false trusts.
Panic is for the live session, not history on disk. Panic closes open editors without saving, clears buffers, and locks the password gate again. Files you already exported stay where you saved them. If those need to go, that is a separate decision.
Weak tools stay weak on purpose in the list. Invert is reversible. Soft blur still leaves structure. Use them for mild cover only. When a region must not come back easy - to an eye or to automated recovery - prefer NULLBURN or a solid Mask, then check the export yourself.
Another copy is out of scope. If the same frame already left your machine, this tool cannot recall it. It only improves what you do with the copy you still control.
CPU, not GPU. Large regions can take a short moment. That is the cost of staying a plain offline script with no heavy runtime.
I built this as a small offline gift for people who live with screenshots as evidence risk. Use it, read it, or ignore it. If it helps .. good
Support / Tips [COLOR=rgb(226, 80, 65)](Optional)[/COLOR]
This project is completely free and open-source. If this tool saves you time, helps protect your workflow, or if you simply appreciate the effort and want to support future tools and development, tips are always appreciated (never expected, but always welcome):
[COLOR=rgb(251, 160, 38)](XMR)[/COLOR]: [COLOR=rgb(250, 197, 28)][ 89QRPNnqCgm6aanvjhby71U2usNS4TfZhBEa72KdcmwnXfi1cHTV5exfozeLLrqpG3YkfjpQefPcfEeUTzuhmcJH4Mi5b7E ][/COLOR]
Files attached: Script,README,Requirements.txt
"Rename the files after download"
09FD-SHIELD.py
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/b61e25465c50652f/a21c9d11a1d59be7.py[/URL]
README.md
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/987c315f7a06b3d3/cb8dc75c6b80bc.md[/URL]
requirements.txt
[URL unfurl="true"]http://eternalcbrzpicytj4zyguygpmkjlkddxob7tptlr25cdipe5svyqoqd.onion/file/4f064bc64aeb69/f511a95a5c0de85f.txt[/URL]
Quote:ʙᴜɪʟᴛ ʙʏ ʜᴀɴᴅ. ᴀɪ ᴏɴʟʏ ꜰᴏʀ ʙᴏʀɪɴɢ ꜱᴛᴜᴄᴋ ᴘᴏɪɴᴛꜱ - ɴᴏᴛ ꜰᴏʀ ᴛʜᴇ ᴅᴇꜱɪɢɴ, ᴛʜᴇ ᴅᴇᴄɪꜱɪᴏɴꜱ