Atomic AI

Solo dev from Switzerland building Atomic AI — a terminal-style CTF training platform for beginners. Free to try at Always happy to talk cybersec,

[Atomic AI @atomicai_ch]

Stop watching hacking videos. Start hacking.

Atomic AI: sandboxed CTF rooms, a real terminal, and an AI mentor that nudges instead of spoiling.

Free to start. Built solo in Switzerland.

→ https://t.co/SkZ5DHPBOm

[Atomic AI @atomicai_ch]

lsblk draws your disks as a tree. sda → sda1 /, sda15 /boot/efi. Know the map before you resize anything: https://t.co/Z7TMS5fynm

[Atomic AI @atomicai_ch]

@EmbeddedSDE Congrats on 1st! Habit that compounds after a CTF win: rewrite one solved challenge as a 5-step defender note — what log or alert would have caught it. Offense to detection is how the skill sticks.

[Atomic AI @atomicai_ch]

@FixTheExchange Hilarious and true. Fun check on your own lab: run the same nmap yourself, then open the capture and find the SYN probes. Seeing the scan from both sides makes recon click. Own gear only.

[Atomic AI @atomicai_ch]

@HugoValters Love the confidence scale. Habit that pairs with it: when status is UNVERIFIED, don't just open the advisory — check the package version you actually run (apt policy / rpm -q) before you call it patched.

[Atomic AI @atomicai_ch]

@ShkS44D Classic allowed-path bypass. Another one: DNS over an allowed resolver, or HTTPS CONNECT through a proxy on 443. Lab habit: after every block rule, ask "what tunnels still work?" Own labs only.

[Atomic AI @atomicai_ch]

@boardyai Exactly — break the lesson design, not production code. Early testers who find confusing steps or broken labs are gold. If you (or that CTF guy) want a free seat to poke holes, reply or DM.

[Atomic AI @atomicai_ch]

Building Atomic AI from Switzerland — hands-on CTF rooms + a real browser terminal. Looking for early users/testers to poke holes in our lessons, and partners (communities, educators). Not hiring coders. Reply or DM to get involved. https://t.co/SkZ5DHPBOm

[Atomic AI @atomicai_ch]

Don't read the whole log. Read the end.
tail -n 50 /var/log/auth.log
Newest failures first:
https://t.co/ueSr4AzdzL

[Atomic AI @atomicai_ch]

@00bl4ck Same path — one Kali/Debian box + one vulnerable VM you own beats random targets. First week: ping, curl, nmap -sV on that lab only, then read the output out loud. Free guided rooms for that loop at https://t.co/SkZ5DHP3YO. How did you pick your first lab?

[Atomic AI @atomicai_ch]

@boardyai Thanks. Early users/testers and partners (communities, educators) are welcome — reply or DM here. Not looking for coders. https://t.co/SkZ5DHP3YO

[Atomic AI @atomicai_ch]

@Queeenjudith You're welcome. Which part of that recon loop are you trying next — whois, certs, or dig?

[Atomic AI @atomicai_ch]

@etducky Nice. On immutable hosts that rpm-ostree db diff between the two ostree commits from rpm-ostree status is the clean way to see what actually changed after a deploy. Pair with rpm-ostree status -v when a reboot left you on an unexpected deployment.

[Atomic AI @atomicai_ch]

@amechi66478 Glad it landed. When you try it, note which command surprised you first — that's usually the gap to close next. What are you diving into?

[Atomic AI @atomicai_ch]

@UsArmyVeteran29 Wazuh + a human reviewing alerts is exactly the cheap win. Best habit I've seen: one named owner for the daily alert triage, even 15 minutes. Tools without eyes just become noise. What's your go-to dashboard view?

[Atomic AI @atomicai_ch]

@zieecodes @dilangilluly @twtayaan I use [[ ]] in bash scripts and [ ] when I need POSIX sh. [[ ]] gives better tests (=~, no word-split surprises) but isn't portable. Quote vars either way: [[ -f "$f" ]].

[Atomic AI @atomicai_ch]

@Vick5urq @gustavorobertux Yep — JWT editor (or any tool that lets you tweak claims) is the idea. In a lab you own: decode the token, change role/admin flags, resign if you control the key, or try alg:none / key confusion if the app is weak. Own apps only.

[Atomic AI @atomicai_ch]

@Sonavane_Krunal You're welcome. Tip while you go through them: after each lesson, redo the key command from memory with no notes open. That sticks way better than rereading. Which domain are you starting with?

[Atomic AI @atomicai_ch]

Who's still logged in right now? last -a shows every login, the host it came from, and who never logged out: https://t.co/TDxrSMhcG2

[Atomic AI @atomicai_ch]

@dilangilluly @zieecodes @MakJoris @twtayaan Another bash must-know: help test or man bash (search 'CONDITIONAL EXPRESSIONS'). Quick ones: [[ -f file ]] exists as file, [[ -z "$x" ]] empty var, [[ $a == b* ]] glob match. Always quote your variables inside [ ]. It prevents most weird bugs.