💩 pooputil
Ever heard of malware?
One of the first things it usually does is scan your drive for common file extensions.
.docx .xlsx .pptx .pdf .jpg .png .zip .zip .txtYour files are predictable.
pooputilchanges that.
pooputil is a small open-source file encryption utility that compresses your files into encrypted .poop containers.
Instead of just hiding files somewhere, pooputil compresses them, encrypts them using AES-256-GCM, derives keys using Scrypt, and securely overwrites the original file after encryption. The compression happens inside the container — no plaintext ZIP ever touches your disk.
Whether youre storing backups, documents or just wanna archive stuff safely, pooputil gives you a Python API, CLI and a simple desktop GUI.
Current Ver v0.1.1
Licensed under GPLv3. Fork it, improve it or build your own project on top of it.
Features
- AES-256-GCM authenticated encryption
- Scrypt (n=2^17) password derivation, params stored in the container header
- Built-in DEFLATE compression inside the ciphertext
- Encrypted folder manifest (names, sizes, mtimes) — restored on decrypt
- Custom
.poopcontainer format, v2 with v1 read-back - Python API
- CLI
- Desktop GUI
- Secure overwrite-based deletion
- Backend separated from GUI
Why .poop?
A lot of malware targets common file extensions.
.docx
.xlsx
.pdf
.jpg
.png
.zip
Those are easy to recognize.
pooputil stores encrypted data inside .poop containers instead.
Will this stop malware?
Probably not.
If malware wants to encrypt every file on your disk itll happily encrypt .poop too.
The idea here isnt to beat malware, its to make your actual file contents unreadable without the password while also giving you a funny file extension.
Fun Fact
The .poop file extension was inspired by No Text To Speech.
If you know, you know.
Architecture
pooputil is split into modules kinda like Arduino.
GUI
│
▼
pooputil.core
▲
│
CLI
│
▼
Python API
The GUI is just a frontend.
Most of the work happens inside pooputil.core, so you can import it directly into your own scripts without dragging GUI stuff along.
Crypto
| Component | Algorithm |
|---|---|
| Encryption | AES-256-GCM |
| KDF | Scrypt n=2^17 r=8 p=1 |
| Salt | 16 bytes |
| Nonce | 12 bytes |
| Authentication | GCM Tag |
| Compression | raw DEFLATE inside the ciphertext |
KDF params and the compression method live in the plaintext header, bound by GCM AAD — so they can be tuned in future versions without breaking old files.
I use the cryptography library instead of trying to implement crypto myself.
Container format
The v2 layout is specced in docs/DOCS.md: a 54-byte authenticated header (magic, version, type, compression method, KDF params, salt, IV, tag), then a single GCM stream. Folder containers embed an encrypted JSON manifest followed by one compressed stream per file.
Old v1 containers (pooputil < 0.2.0) still decrypt.
Secure deletion
After encryption pooputil overwrites the original file before deleting it.
Decryption works the same way in reverse: once your data is restored, the .poop container is overwritten and removed. So decrypting a container consumes it — keep a copy if you want to decrypt it twice.
Keep in mind secure deletion depends on your filesystem and storage device SSDs especially don't always behave the same because of wear leveling
Installation
pip install pooputil
Usage
GUI
pooputil-gui
or
python -m pooputil
CLI
Encrypt (interactive — the password is hidden and confirmed twice, so a typo cant nuke your original)
pooputil-cli --encrypt "/path/to/data"
Decrypt (interactive)
pooputil-cli --decrypt "/path/to/data.poop"
Non-interactive (for scripts — note that --password shows up in your shell history, which is why the prompt exists)
pooputil-cli --encrypt "/path/to/data" --password "SuperSecretKey99"
pooputil-cli --decrypt "/path/to/data.poop" --password "SuperSecretKey99"
Or via environment variable
POOPUTIL_PASSWORD="SuperSecretKey99" pooputil-cli --decrypt "/path/to/data.poop"
Python API
from pooputil import core
password = b"SuperSecretPassword"
target = "./important.docx"
if core.is_safe_path(target):
core.encrypt_target(target, password)
else:
print("Unsafe path.")
Decrypt
from pooputil import core
restored = core.decrypt_target(
"./important.docx.poop",
b"SuperSecretPassword"
)
print(restored)
Disclaimer
This project is meant for legitimate encryption and backup purposes.
Also...
Dont forget your password.
I cant magically decrypt your .poop if you lose it.
You cant unflush a poop if you flushed it.
License
GPLv3.
Release files for pooputil 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pooputil-0.1.1.tar.gz | 27.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pooputil-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.2 kB
Release files / pooputil-0.1.1.tar.gz
| Download URL | pooputil-0.1.1.tar.gz |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
012e7b78fba78df71fffaf2781bfc966c5f62e4fe675c9397094f1f941e25b3a
|
|
BLAKE2b-256 checksum How to use checksums |
50e554c2a2ca93dfd7553cd52f7880ed997a76a46dca0cc8b51ba84c4cee4727
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency logRelease files / pooputil-0.1.1-py3-none-any.whl
| Download URL | pooputil-0.1.1-py3-none-any.whl |
|---|---|
| Size | 24.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2793ddd6516c54bbdc91cd444f1d63c82f473f0f72b68a8c12f08762ff1472a
|
|
BLAKE2b-256 checksum How to use checksums |
c1b613a5af72b58de655745bb4a9e67551578d1599ccb019809c6c9ce63d0ca4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency log