Independent | Top 60 Bugcrowd | OSCP, CRTO, eWPTX, eCPTX | https://xitter.cf/t.co/VA42ZpFqGJ | https://xitter.cf/t.co/yHuJFexKd1 (Bahasa Indonesia) Free!

Jakarta
Joined September 2012
Bismillah. Here is the simple write-up about how I found an RCE (from outdated apps). "From Recon to Optimizing RCE Results - Simple Story with One of the Biggest ICT Company" medium.com/@YoKoKho/from-rec… Note: not much new things. Just using lots of published tips and tricks.
12
172
6
378
YoKo Kho 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,541
1,500,009
YoKo Kho retweeted
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?
711
3,863
646
36,646
4,770,335
YoKo Kho retweeted
Introducing PwnEscape 🦉: a full KVM guest-to-host escape via a Linux kernel networking flaw affecting industry standard hypervisors. CVE-2026-99999 went from untrusted VM code to host-kernel memory reads, controlled writes, and root command execution. More below:
🤖 Made with AI
16
220
46
1,275
389,749
❗️ Researchers at ThreatFabric found a new Android trojan swaps the apps of seven Indonesian banks for patched copies that blind their security checks. Even Google's Play Integrity checks go to an attacker server that hands back the verdict.
16
225
26
767
116,484
Currently the number ONE trending repo on GitHub: Reverse Engineer Anything. It lets your agent take a feature you want from another app and work out how it's built without ever seeing the source code. Software is dead, long live software!
45
404
41
4,603
153,891
YoKo Kho retweeted
How to use LLMs for vulnerability research by @ZephrFish (Andy Gill) MCP: blog.zsec.uk/bullyingllms/ Harness: blog.zsec.uk/harnessing-harn… #infosec #llm
4
129
1
681
31,697
YoKo Kho retweeted
Made over $25K hacking marketplace app permission issues across various bug bounty programs. Here's my latest writeup on how a malicious app might take over a GitHub repository: jeetbhdr.github.io/github-gr… #bugbounty
12
43
447
12,837
YoKo Kho retweeted
I've never worked on WhatsApp before, so I thought it'd be interesting to poke it with a stick! I wrote an article about my attempt to uncover WhatsApp's CVE-2026-23866: numb3rs.re/posts/cve-2026-23… This is my first article on mobile VR, let me know what you think!
3
54
2
252
19,847
YoKo Kho retweeted
AI security stack is getting f...cking important 10 open-source GitHub projects for letting agents use real tools without giving them the keys to EVERYTHING 01 E2B ▸ github.com/e2b-dev/E2B → isolated sandboxes for agent execution 02 gVisor ▸ github.com/google/gvisor → sandbox untrusted workloads ISOLATE THE AGENT 03 Firecracker ▸ github.com/firecracker-micro… → lightweight microVM isolation 04 Kata Containers ▸ github.com/kata-containers/k… → containers with VM-level isolation CONTROL THE TOOLS 05 Open Policy Agent ▸ github.com/open-policy-agent… → policy checks before actions execute 06 Casbin ▸ github.com/casbin/casbin → permissions + access control PROTECT THE SECRETS 07 Infisical ▸ github.com/Infisical/infisic… → secrets management for AI infrastructure 08 SOPS ▸ github.com/getsops/sops → encrypted secrets inside repos WATCH WHAT HAPPENS 09 Falco ▸ github.com/falcosecurity/fal… → detect suspicious runtime behavior 10 Trivy ▸ github.com/aquasecurity/triv… → scan code + containers + infrastructure the security loop: request → permission → sandbox → tool → execute → inspect → allow / block → log 3 layers I'd actually build: agent: E2B → OPA → Casbin runtime: Firecracker → Falco → Trivy secrets: Infisical → SOPS and this is where it gets interesting: giving an AI agent more tools makes it more useful it also gives it more ways to break something the next agent stack isn't just memory + tools + reasoning it needs permissions ⭣
33
83
1
550
27,273
YoKo Kho retweeted
APT Encyclopedia Threat Intelligence Database cyllex.io/encyclopedia/
6
153
2
683
29,387
YoKo Kho retweeted
From AI Agents to RCE - Building a Vulnerability Research Workflow blog.quarkslab.com/from-ai-a…
2
78
418
28,064
YoKo Kho retweeted
⚠️CVE-2026-18963 (CVSS 9.1)⚠️ Critical Unauthenticated Account Takeover vulnerability in Keycloak’s reset-credentials flow. In affected Keycloak 26.x versions, unauthenticated attackers can bypass email verification during password recovery and continue the reset-credentials flow. This allows an attacker who knows a target username or email address to set new credentials without accessing the victim’s email, resulting in full account takeover. Patched versions include 26.4.15, 26.6.6, and 26.7.2. Users should upgrade to a fixed release. 🔥PoC + Vulnerable environment: github.com/EQSTLab/CVE-2026-… #Keycloak #AccountTakeover #AuthenticationBypass #PasswordReset #CWE640 #CyberSecurity #CVE #PoC #Exploit #CVE_2026_18963
6
48
2
319
28,419
YoKo Kho retweeted
有人把自己逆向一堆 APK 的经验,炼成了一个 Skill,开源了! 装上之后,AI 就能按老手的思路去分析安卓 App。 它能帮你: 1. 改 dex、重新打包签名 2. 处理加壳和加载器 3. 分析 native 层 4. 啃 Flutter 的 Dart AOT 几个细节: - Claude Code、Codex 都能直接用 - 不打包工具,AI 会自己装 frida、jadx、blutter - 任务一开头就让模型用这个 Skill,效果最好 GitHub 1.4k 星,MIT 协议: github.com/newliver666/apk-r…
38
411
7
2,719
141,997