🇸🇦 Vulnerability Research • Reverse Engineering • 0days Trust the evidence Question everything else.
SAUDI ARABIA
Joined February 2026
- Tweets204
- Following377
- Followers13.9K
- Likes1K
for the idiots trying to convince people that 14.02 has already been achieved
let me remind u of one simple thing
if u dont see clear proof of userland like an actual notification showing on the console and u dont see hen being loaded or something equivalent then dont believe the idiots promoting themselves
claims are easy
proof is what matters
the bd-j file currently being shared for ps4 14.00 is originally my private file it was unpacked and redistributed and whoever did it was stupid enough to leave references to my own domain inside it
the only reason this file ever left my hands was because someone with devkit and testkit access contacted me and offered to support my research with a testkit dev resources firmware updates and anything i needed in return he wanted access to my jailbreak for testing i agreed because i wanted to study the security differences between retail consoles and dev/test hardware and nothing more
later i spent around two weeks researching a separate method related to extracting content_key_seed information for sony packages zeco @notnotzecoxao helped me with some fundamentals corrected some information and gave me some keys and i will never deny that after the method was completed we agreed to keep it private between us
after that other people kept asking me for the method and keys and i refused but later i found out the method had been shared outside that agreement and then the same private circle that already had my iso started getting more information too
after giving people far too much trust i can say this with confidence in my own work i always wanted to do things the right way and responsibly but mistakes happen and this was one of mine i trusted the wrong people
the key extraction vulnerability has now been reported to sony as well :) the report is submitted and sony will also be provided with the list of games they obtained content_key_seed from so they can investigate the full impact
i have also provided the relevant technical details and evidence through the proper channels including information that can help them verify where the leaked development material came from
i will not publish private mac addresses serial numbers account details or personal information publicly that belongs with sony not social media
from this point forward im done with playstation research im not working on playstation anymore and im leaving this shitty scene completely
i came here to research build and learn not to deal with leaks lies black market drama and people selling private work behind each others backs
goodbye to fpkg updates :)
and this is officially the end of the keys business
im out
i think zeco needs his own spot here 😂
psdevwiki.com/ps4/Wall_of_Sh…
and under the description just put
“breaks agreements leaks private stuff then says im bipolar”
people need to understand this properly before getting excited over a notification popup
sony changed libkernel.sprx on the newer firmware in a way that removed the useful kernel facing paths that could actually help you reach sensitive syscalls and kernel functionality and they left only the normal stuff games still need like notifications and basic system functions
so yes the lua entry can still work in userland and yes u can send notifications and execute some basic things but that does not mean u bypassed the kernel and it does not mean u suddenly have a kernel exploit
libkernel.sprx is basically the bridge used by games and sony stripped the sensitive parts that matter for this kind of exploitation while keeping what normal games still need
sending a notification is just sending a notification
thats it
u cannot take that and claim full kernel bypass on the latest firmware
before claiming something like this go read libkernel.sprx properly understand what sony removed understand what is still exposed and understand what actually reaches the kernel
and collecting donations while showing public code that gives people the impression u achieved something u didnt actually achieve is not acceptable at all
research is fine
testing is fine
being wrong is fine
but misleading people and making big claims around something this basic is not
always follow people who show real reproducible technical proof
and for u specifically read libkernel.sprx first and understand the path properly before claiming u reached something bigger than what u actually did
small clarification
i was contacted by a third party who told me that the original owner of this bug was not gezine as some people were saying and he was very clear about that
he also told me the bug had been known privately for years but he refused to tell me who the original owner actually was
so to whoever really owned it and had it first if this message reaches you i want to say sorry i honestly did not know and if i had known from the beginning i would not have reported it
i never wanted to step on someone else’s work or take credit away from anyone
this is exactly what happens when the scene is split into private circles and every group keeps everything to themselves people outside those circles have no idea who discovered what and then situations like this happen
too much separation creates confusion unnecessary conflict duplicated work and people blaming each other later for things that could have been avoided with better communication
so again to the original researcher whoever you are you have my respect and my apology
and i hope one day this scene becomes less divided because everyone would benefit from that
just to be clear i am talking about the bd-j userland bug that stayed working for me across 13.60 14.00 and 14.10 and was finally patched in 14.20
and out of respect for the original researcher i will not publish it publicly or release any details about it
if he ever decides to release it thats completely his choice
oob read is working :) in bdj userland
oob write is patched and i think there is way to bypass it let's see for 1420