Nürnberg
Joined April 2009
Alexander K. retweeted
🚨 CISA adds two PHP2Shell bugs to its KEV catalog after confirming active exploitation. CVE-2026-109618 and CVE-2026-109619 enable unauthenticated remote code execution on affected PHP deployments. Read ↓ thehackernews.com/2026/10/ci…
25
62
3
227
40,166
🚨 PHP2Shell attackers accessed MFA secrets and password hashes at a European government entity in just 2 hours. That's not all. → Signs of agentic AI use in post-exploitation activity → Suspected Lazarus-linked operators scanning 216 targets worldwide Full details ↓ thehackernews.com/2026/10/ph…
52
290
53
1,173
171,440
You don’t need an enterprise budget to build meaningful resilience. Tomorrow on #CISALive, discover no-cost CISA tools, scanning services, and tabletop exercises designed to help resource-constrained operators stay mission-ready. 🔗 Join live: linkedin.com/events/75180356…
19
37
9
148
37,259
Alexander K. retweeted
cvENGINE은 인터넷에 노출된 자산을 자동으로 검색하고 매핑하며, 발견된 모든 서비스와 버전을 식별하고, 현재 악용되고 있는 CVE 중 어떤 것이 실제로 영향을 미쳤는지 알려줌 도메인, 서브도메인, IP 주소, 포트, 제품, 버전, TLS 및 기술 정보가 자동으로 검색되어 Shodan 스타일의 인벤토리에 저장 github.com/hevnsnt/CVEngine
3
25
120
6,479
Alexander K. retweeted
Adversaries may gain access to NSS and DIB network devices through SNMPv1 and SNMPv2c read-write community strings. Keep your networks secure by upgrading to SNMPv3 which includes encryption and authentication. media.defense.gov/2022/Jun/1…
22
118
13
432
37,299
Alexander K. retweeted
VIPER 는 강력하고 유연한 레드팀 플랫폼 공격자 시뮬레이션 및 레드팀 작전에 필요한 핵심 도구와 기능을 통합하여 사이버 보안 평가 작업을 효율적으로 완료할 수 있도록 지원 MITRE ATT&CK 프레임워크의 모든 단계를 포괄하도록 설계된 즉시 사용 가능한 레드팀 도구로 , 포괄적인 공격 시뮬레이션 솔루션을 제공 github.com/FunnyWolf/Viper
3
26
1
96
5,584
Alexander K. retweeted
THE COMPLETE AI REVERSE-ENGINEERING TOOLKIT: 150+ FREE RESOURCES Agents, free courses, native binaries, .NET, iOS, Electron, browsers, firmware, WASM and protocols, and most builders have no idea it's all free 01 - START WITH REA Installation and agent setup github.com/morluto/rea/blob/… Your first REA investigation rea.tools/first-investigatio… REA guides rea.tools/guides/ Guided MCP prompts github.com/morluto/rea/blob/… MCP runtime contracts github.com/morluto/rea/blob/… Also useful: Evidence Workflows · Native Investigation Guide · JavaScript Application Graph · Electron Observation Guide Install: npx rea-agents@latest setup 02 - REAL REA INVESTIGATIONS Notes Export - button → IPC → CSV rea.tools/first-investigatio… Notion Clipboard - page API → preload → main process rea.tools/showcase/notion/ DX-Ball - Windows binary → verified C function rea.tools/showcase/dx-ball/ Aegis - APK → TOTP implementation rea.tools/showcase/aegis/ Also useful: CTF Flag Checker · REA Gems · Chrome Dinosaur investigation · Notes Evidence Record 03 - AI REVERSE-ENGINEERING AGENTS IDA Pro MCP github.com/mrexodia/ida-pro-… GhidrAssistMCP github.com/symgraph/GhidrAss… GhidraMCP github.com/LaurieWired/Ghidr… Official radare2 MCP github.com/radareorg/radare2… Also useful: Revenant · Awesome LLM Reverse Engineering · AgentRE-Bench · SRE-Bench · Reverse Engineering Agent Skill 04 - NATIVE BINARIES Ghidra github.com/NationalSecurityA… radare2 github.com/radareorg/radare2 Rizin github.com/rizinorg/rizin Cutter github.com/rizinorg/cutter Also useful: Keystone · GNU Binutils · GDB · LLDB · pwntools · ROPgadget · Detect It Easy · capa · YARA 05 - .NET APPLICATIONS ILSpy github.com/icsharpcode/ILSpy dnSpyEx github.com/dnSpyEx/dnSpy dnlib github.com/0xd4d/dnlib de4dot github.com/de4dot/de4dot Also useful: AsmResolver · Harmony · Mono.Cecil · NativeAOT reversing helpers 06 - iOS Frida iOS Guide frida.re/docs/ios/ OWASP iOS Testing Guide mas.owasp.org/MASTG/0x06b-Ba… DVIA-v2 github.com/prateek147/DVIA-v… libimobiledevice github.com/libimobiledevice/… Also useful: ios-deploy · class-dump · ipsw · Objection iOS 07 - ELECTRON AND JAVASCRIPT Electron ASAR github.com/electron/asar Electron Process Model electronjs.org/docs/latest/t… Source Map Explorer github.com/danvk/source-map-… AST Explorer astexplorer.net/ Babel Parser github.com/babel/babel/tree/… Also useful: Electron Security Guide · source-map · Esprima · Acorn · JS Beautifier 08 - BROWSERS AND WEB APPS Chrome DevTools Protocol chromedevtools.github.io/dev… Chrome DevTools developer.chrome.com/docs/de… Puppeteer github.com/puppeteer/puppete… Playwright github.com/microsoft/playwri… Also useful: OWASP ZAP · HTTP Toolkit · WebSocket King · Firefox DevTools · HAR Specification 09 - FIRMWARE AND DEVICES Binwalk github.com/ReFirmLabs/binwal… EMBA github.com/e-m-b-a/emba FACT Core github.com/fkie-cad/FACT_cor… FirmAE github.com/pr0v3rbs/FirmAE Also useful: sasquatch · ubi_reader · Jefferson · Firmware Mod Kit · Firmware Analysis Toolkit · Revenant 10 - WEBASSEMBLY WABT github.com/WebAssembly/wabt Binaryen github.com/WebAssembly/binar… wasm-tools github.com/bytecodealliance/… Also useful: Wasmtime · Wasmer · wasm-decompile · wasm2c 11 - NETWORK PROTOCOLS Wireshark gitlab.com/wireshark/wiresha… Scapy github.com/secdev/scapy Zeek github.com/zeek/zeek Boofuzz github.com/jtpereyda/boofuzz Also useful: tcpdump · PcapPlusPlus · Construct · Netzob · Wireshark Display Filters 12 - FREE COURSES AND PRACTICE OpenSecurityTraining2 x86-64 Assembly p.ost2.fyi/courses/course-v1… pwn.()college Reverse Engineering pwn.college/cse365-s2026/mod… pwn.()college Reversing Hell pwn.college/reversing-hell/ Malware Unicorn RE101 malwareunicorn.org/workshops… Also useful: RPISEC Modern Binary Exploitation · UMass Reverse Engineering · OpenSecurityTraining Intro x86 · crackmes.()one · Microcorruption · Flare-On · Malware Traffic Analysis · OWASP MASTG · OverTheWire · PicoCTF THE FASTEST PATH Install REA → investigate one feature → collect Evidence → trace the complete function → write a clean-room specification → build an independent implementation → compare it against the authorized original → keep every failure and unknown visible Start small: Notes → Notion → CTF binary → Aegis APK → DX-Ball → firmware, protocols and real applications Save this. Pick one target. Reverse engineer one feature.
REA hit #1 on GitHub trending, and most people still run it inside a single chat Split it into 4 subagents and one command takes a program you own from sealed binary to a tested rebuild with a match rate Set it up once, aim it at the next one:
13
105
2
679
20,809
Alexander K. retweeted
i'm open sourcing UNBROKER: a tool that finds where your personal info is exposed by data brokers and files the removals for you it runs as a skill in Hermes Agent _________ your data is everywhere; hundreds of brokers publish your name, current and old addresses, phone, email, birthday, even your relatives. anyone can find where you live in about ten seconds CCPA, CPRA, GDPR, and a growing number of state laws say a broker has to delete your data if you ask. there's just no easy bulk button. every broker has a different process and many make it intentionally difficult to exercise your right to delete this is the entire business model for companies like DeleteMe, Incogni, EasyOptOuts; they charge you monthly (DeleteMe is $330/yr for a Family plan) to file removals that you can submit yourself for free, and then you're giving a new company the exact data you want to erase so i built one you just run for free. your data never even has to leave your machine if you run a local model _________ how it works: first it builds search vectors from everything: every name, alias, email, phone, and address you've had (brokers might index you under a maiden name or a house you left in 2014, so the naive "current name + current city" approach can miss profiles). then it fans out parallel sub-agents across the broker list, which refreshes from a maintained public source automation is tiered. when it can handle a broker end to end with your settings, it drives a browser through the opt-out form, sends the email, and opens the confirmation link itself. soft CAPTCHAs clear on their own with a real browser. anything only a human can finish comes back to you as a short list at the end the email side doesn't need a stored password and can send opt-outs and open verification links through your own logged-in webmail. you can also wire up SMTP, or keep it manual and just send the drafts it writes it tailors every request to your jurisdiction, filing under the framework that applies where you live: CCPA and CPRA in California, GDPR in the EU and UK, a general right-to-delete request everywhere else. if you're in California it also uses the state's DROP portal, a single request that covers 500+ registered brokers at once it holds as little of your data as it can, and keeps it local. dossiers are encrypted at rest if you want, opaque ids keep your real name out of every filename and log, and nothing leaves your machine unless you opt in brokers sometimes relist you eventually or new ones find your data, so every case is tracked in a ledger and can be re-scanned on a cron schedule so if your data pops back up it files the removal again github.com/NousResearch/herm…
112
324
44
3,595
686,564
Alexander K. retweeted
If you've ever wondered why smart TVs are so cheap, this is why. @log4j rooted his Samsung and found an always-on hot mic, automatic content recognition, geolocation, network mapping, ad targeting and user profiling, shared with Samsung's "400 partners". A lot of it can be blocked in <15 min, wrote a basic guide below. What your TV is doing The main culprit is ACR (automatic content recognition). Your TV screenshots what's on screen, fingerprints it, and sends it home to build your ad profile. Samsung does it every 500ms, LG every 10ms [1]. What is insane: it happens on connected devices too. Plug in your laptop, your console, your work machine, and your TV can fingerprint that via HDMI [1]. He also found that if your Samsung doesn't have a mic, it'll look for one from a connected soundbar or bluetooth device. xitter.cf/log4j/status/211376224… It's on by default, and you likely agreed to it on the setup screen you clicked through in 10 seconds. Step 1: Turn off ACR Samsung: Terms & Privacy → Viewing Information Services LG: Live Plus Vizio: Viewing Data Roku: "Use info from TV inputs" Sony/Google TV: Samba Interactive TV Menus vary by model, but those are the names to look for. While you're in there, opt out of interest-based ads, reset your advertising ID, decline every optional privacy agreement, turn off voice recognition, and delete apps you never open. Step 2: Give smart devices their own network Put the TV, cameras, speakers and vacuum on your router's guest/IoT network. The logic is simple: these devices rarely get patched. If one gets compromised (getting drastically more frequent with AI), it shouldn't be able to see your other devices or home network. Step 3: Block trackers for the whole house with DNS-level filtering NextDNS (cloud-based) is easy and has a solid free plan. Pi-hole is a little bit more work if you prefer self hosting. For simplicity we'll focus on the former. 1. Sign up at nextdns.io (free tier is plenty) 2. Privacy tab: add a blocklist (OISD is a good bet) and turn on Native Tracking Protection for Samsung, LG, Roku, Amazon (see attached image) 3. Setup tab: copy your endpoint 4. Paste it into your router's DNS settings as DNS-over-HTTPS/TLS (or use the IPs + "Link IP" if your router only does plain DNS) 5. Bonus: block outbound port 53 except to your router. Some devices hardcode their own DNS to get around you Then open the NextDNS logs and watch how often your TV phones home. It's eye-opening. If an app or update breaks, find the domain in the logs and allowlist it. Why they do this TV prices are down 97% since 2000 [2]. Most of that is better manufacturing and brutal competition. But once margins on the hardware hit zero, the cost moved to you. In Q3 2024, Vizio lost $6.7M selling TVs and made $115.8M in gross profit from ads and viewing data [3]. They've said on earnings calls that they keep TV prices low to grow the audience they sell to advertisers. Walmart bought them in 2024. This isn't a conspiracy theory either. Vizio paid $2.2M to the FTC in 2017 for tracking 11 million TVs without consent. Last December, Texas sued Samsung, LG, Sony, Hisense and TCL over ACR. Samsung and LG have since agreed to stop collecting that data without explicit consent [4]. TL;DR 1. ACR off 2. Ads + voice off 3. Smart devices on their own network 4. NextDNS filtering on the router Sources: [1] ACR study: arxiv.org/abs/2409.06203 [2] Cost of US consumer goods: aei.org/economics/chart-of-t… [3] Vizio Q3 2024: sec.gov/Archives/edgar/data/… [4] Texas v. Samsung: texasattorneygeneral.gov/new…
i own a relatively new (2025) samsung tv. i kept getting weirdly targeted ads. i tried reversing the firmware but it was aes encrypted and no keys unless tear it apart and do uart/jtag magic. zero days it is. root shell on new samsung TVs! discovered PRIVACY HORROR. write up?
347
3,269
339
22,540
1,500,474
cvENGINE: the most advanced external attack surface assessment you can get for free. Point it at a domain: bbot, nmap, and Nuclei map your attack surface, then an AI proves which CVEs can actually hit you with read-only checks. github.com/hevnsnt/CVEngine
16
146
4
971
73,080
🚨 Two critical PHP core vulnerabilities (CVSS 9.2) expose web apps to RCE and memory disclosure across PHP 5.4–8.5.11. Use our guide to patch and hunt for compromise. @googlecloud advisory: goo.gle/4idT13I @wiz_io research: goo.gle/4BiQgGX
3
44
3
115
8,459
Current information I have on php2Shell: - The RCEs requires the attacker to obtain memory addresses which are typically protected by ASLR. - I suspect the original author (lcfr_hax) likely has a reliable exploit which leads to stable code execution. - Most of the PoCs being posted are completely non-functional AI slop. - There is at least 1 working non-slop exploit being passed around, but it's reliant on bruteforcing for ASLR bypass, so not particularly impactful. - Rumor of ITW exploitation are patchy. There are attempts being seen using the non-functional leaked RCE, or variants that are config / system specific. - Some rumors point towards a known-working exploit being used by threat actors (I've personally confirmed this specific exploit works, but the ASLR bypass technique is unreliable at best and massively limits the potential impact). - I'd expect heavy ITW exploitation in the next few weeks based on how many people are looking at this. Though, success rates will vary heavily based on the specific exploit chain.
24
194
19
1,426
124,939