Your laptop already knows who's snooping through it. It just isn't telling you.
I got tired of Windows' "security" being a login screen anyone can brute-force with the family dog's name. So I built ATLOCK — a total security suite for Windows that doesn't just lock things, it catches whoever tries to get past the lock.
Three wrong password attempts on a guarded file, and ATLOCK has already taken their photo, recorded 10 seconds of video, sounded an alarm, and dropped the evidence straight into your gallery.
This is v4.0. Free, self-contained, and honestly a little unhinged in the best way.
What ATLOCK actually does
🔒 Lockdown A full system-level screen lock with a live countdown ring and OS-level hardening underneath it — not just a tkinter window sitting on top of your desktop pretending to be secure.
🗂 File Guard This is the part I'm most proud of. Instead of just hiding a file behind a password prompt (which anyone can ls around), File Guard drops down to Windows NTFS ACL permissions and actually strips read access at the filesystem level. If someone tries to open a guarded file outside the app, Windows itself says no.
🔑 Password Vault An encrypted store for the stuff you'd never want in a plaintext .txt file — emails, UPI PINs, recovery codes. Encrypted with Fernet (AES-128-CBC + HMAC), with your master password run through PBKDF2-HMAC-SHA256 at 200,000 iterations and a random salt. No plaintext ever touches disk.
📸 Intruder Ops The feature that makes people go "wait, it does what?":
1st wrong password → silent photo capture via webcam
3rd/4th wrong attempt → 10-second video capture + audible alarm
Everything lands automatically in Pictures/ATLOCK Security and Videos/ATLOCK Security
⚙️ Settings Toggle capture behavior, pick your gallery folder, tune it to how paranoid you actually want to be.
The security engineering behind it
I didn't want to just wrap a password prompt in a nice UI and call it a security app, so a chunk of v4 went into actually hardening the thing:
Even failed password attempts are masked before they're ever written to a log file — plaintext guesses never persist anywhere, not even in your own logs.
Alert credentials (for things like notification delivery) are encrypted with a machine-bound key, so a copied config file is useless on another machine.
Windows toast notifications are built without string interpolation into the underlying PowerShell call, closing off a class of injection bugs a lot of "just get it working" implementations miss.
None of this makes the app invincible — no local app running on a machine the attacker can also access ever is — but it means the crypto and the OS integration are doing real work instead of security theater.
Stack
Python · customtkinter · OpenCV (for camera/video capture) · cryptography (Fernet + PBKDF2) · pywin32 (native NTFS ACL manipulation) · PyInstaller (packaged as a standalone .exe)
pip install customtkinter pillow opencv-python cryptography pyinstaller pywin32 numpy
python ATLOCK_v4.py
👀 A glimpse of what's next — ATLOCK v5
v5 is already about 30% built, and I'm not going to spoil the whole thing — but here's what's cooking:
Encryption jumping from Fernet AES-128 → AES-256-GCM with machine-bound key derivation
A completely reworked Intruder Ops pipeline
Telegram Sentinel — real-time intrusion alerts pushed straight to your phone, wherever you are
A rebuilt, even darker premium black-and-gold UI
Guarded-file capacity roughly 3x higher than v4
More glimpses soon. If v4 already made you paranoid about your own laptop, v5 is going to make you paranoid about everyone else's.
Try ATLOCK v4, break it, tell me what's missing. Drop a ⭐, open an issue, or just roast the UI in the comments — I read all of it.
🔗 https://github.com/Akhouri-Anmol-Kumar/ATLOCK
Built solo by Akhouri Anmol Kumar under Akhouri Systems.
ATLOCK
"We Build What Others Forgot To Fix"
Top comments (0)