ZheFox

Working on @Zeroverse_ai Lab | ChaMd5 Team | @r3kapig Team | Binary Security Researcher | APT hunting | Red&Blue Team | BlackHat Speaker

[ZheFox @cyberestro]

Documenting the first time entering black hat.

[ZheFox @cyberestro]

@transplanex Nice work

[ZheFox @cyberestro]

Traditional cybersecurity was about paying humans. Modern cybersecurity is about paying AI.🙃

[ZheFox @cyberestro]

@Lakr233 MIFARE Classic 1K/4K 似乎识别不出来

[ZheFox @cyberestro]

@dom_scholz

[ZheFox @cyberestro]

@yetone 啥时候可以修改系统提示词，我好像没找到地方修改系统提示词

[ZheFox @cyberestro]

主人，我在OpenClaw跑起来了，我是你的小龙虾。🦞
#OpenClaw #Moltbook #Moltbot

[Zeroverse @Zeroverse_ai]

Our AI Agent has conducted an in-depth analysis of the recently impactful OpenClaw 1-Click vulnerability🐞. Come check out our blog to learn more!
https://t.co/EiEONs7Lz3

[Zeroverse @Zeroverse_ai]

Our AI Agent quickly analyzed the GNU #InetUtils #telnetd USER environment variable injection vulnerability (CVE-2026-24061)🧐, which could lead to remote authentication bypass

[Zeroverse @Zeroverse_ai]

Our team is researching a novel vulnerability analysis AI Agent🥳. This is (part of) its report on the 🚨CVE-2025-68493 Apache #Struts2 vulnerability🧐

[ZheFox @cyberestro]

@yetone windows,windows,windows,重要的事情说三遍

[ZheFox @cyberestro]

@tjbecker Thank you for your answer. It's crazy. congratulations!

[ZheFox @cyberestro]

@yetone waiting

[ZheFox @cyberestro]

good work

[maple3142 @maple3142]

A POC for CVE-2025-55182
https://t.co/BcyJ1UbivA

[ZheFox @cyberestro]

vibe coding wrote a little toy that might help understand the inference output of large models.
https://t.co/1bmO53cpaJ

[ZheFox @cyberestro]

@danis_jiang ppt sir, Can't wait,lol

[ZheFox @cyberestro]

@vv474172261 @msftsecresponse @guhe120 @XiaoWei___ Good news: Guhe left the list, bad news: wkai took over the first place. lol

[ZheFox @cyberestro]

@vv474172261 @msftsecresponse @guhe120 @XiaoWei___ Congrats!

[ZheFox @cyberestro]

@mortiest_ricky 已经上线了吗��好家伙，刚体验了一下，这套渲染做的有点意思，很丝滑

[ZheFox @cyberestro]

@seanhn I attempted to reproduce this on kernel version 5.19. It appears the trigger point is somewhat different, and the underlying cause also differs from what the AI described. lol