Learn Gemini CLI commands: /, @, and !

𝐑𝐞𝐟𝐥𝐞𝐜𝐭𝐢𝐯𝐞 𝐂𝐨𝐝𝐞 𝐋𝐨𝐚𝐝𝐢𝐧𝐠 (𝐩𝐚𝐫𝐭 3) Demonstration of my NT API reflective code loading attack. I can think of so many ways to expand upon this. In this case I am using a simple meterpreter shellcode although in production I would use a custom reverse shell, probably catch it with nc or something similar… or even better a TactixC2 server (multi-threaded). In time I might open the GitHub repo to public. For anyone interested here is the link to the full video demo: 🔗 https://lnkd.in/dA4JXPzh See my earlier posts on reflective code loading for a more in depth explanation of the technique. (MITRE ATT&CK, Technique T1620)

SSH-Snake: A self-propagating, self-replicating, file-less script that automates the post-exploitation task of SSH private key and host discovery. GitHub: https://lnkd.in/gmbQ8PQ5

ORDS REST Account is Locked (HTTP Status Code: 570) 🚫🔒 but APEX is working? 🤔🛠️ Identifying the user to unlock 👤🔓 https://lnkd.in/e2vtKxhv #orclapex

We built the safety layer for your coding agent 🛡️ 90% of our coding is done using agents like Claude Code and Gemini CLI at Superagent (YC W24). They’re powerful, but without guardrails you have no real control or visibility. 🖖 Introducing VibeKit CLI It wraps your coding agent so you can:   ✅ Run them in an isolated Docker sandbox   ✅ Redact secrets before they leak   ✅ See every file read/write, shell command, and API call   ✅ Keep it local, offline, open source Here’s what it looks like when an agent runs through VibeKit 👇

4 CLI tools I rely on for swift incident checks: - **whois** - **dig** - **curl -I** - **strings** Share your essential CLI commands below! 👇

 Daemon Threads Background service threads (e.g., GC) JVM exits when only daemon threads remain Must call setDaemon(true) before start() ❌ Not good for file I/O or DB writes Thread t = new Thread(task); t.setDaemon(true); t.start();

No more crashing out when your code crashes. Claude code can now run tasks in the background! How? Claude will run bash commands in the background and monitors their logs in real-time. When something breaks, Claude can search the logs for the issue and fix it. No blocked workflows when you’re waiting on long-running tasks, just start up your dev server, move it to the background, run tests or debug in real-time. 

🔹 Detection 1.37 — Suspicious Use of whoami via cmd.exe MITRE Technique: T1033 – System Owner/User Discovery 👉Attackers use whoami to learn about the current user context after gaining access. 👉This is useful for privilege escalation decisions. 🔹 Detection 1.40 — Use of Invoke-WebRequest in PowerShell MITRE Technique: T1105 – Ingress Tool Transfer 👉Invoke-WebRequest is commonly used in PowerShell to download payloads or interact with C2.  👉This detection reveals PowerShell-based download activity.

Did you know a simple YAML file could open the door to remote code execution? Abhay Bhargav walks through a real hands-on lab on Insecure Decentralization, showing how a tiny misconfiguration in YAML parsing can compromise your entire backend server. That’s the power of hands-on labs: in just 20 minutes, you don’t just learn theory, you experience attacks. Check out the full video 👉 link in the comments.

Just pushed my latest BYOVD read and write primitive PoCs to GitHub. The repo includes proof of concept code for: - Removing Kernel Callbacks (See screenshot) - Changing Process Protection Levels    - Disable Runasppl LSASS protection - Disabling ETW providers - Change process token    - Privilege escalation to system    - Downgrade EDR's token - Disable DSE in case VBS is disabled and load unsigned driver https://lnkd.in/e3Q6VFxh Give it a star if you find it useful!