In PS5 hacking information this week, compiled payloads for individuals working BD-JB and a few updates on libhijacker, the PS5 Homebrew “library”.
BD-JB Payloads Compiled
PS5 scene developer John Tornblom has launched a compiled model of the payloads he maintains together with his BD-JB PS5 SDK. The payloads are varied items of executable code you’ll be able to run on a PS5 after triggering the BD-JB exploit (to my data these will not be suitable with the Webkit exploit in the meanwhile, though that might change ultimately if the webkit model of the kernel exploit will get up to date).
These payloads will not be new, however these of us who had been drained to search for compiled variations in random corners of the web might be pleased to search out them instantly on the supply. These payloads embody an elf loader, varied samples to check the SDK (hi there world, sprx loading, arbitrary syscall execution, and so on…), a kernel dumper, Hardware data (CPU Temperature, Frequency, and so on…), and extra. (Notably, no FTP server in there).
John has additionally used the chance to wash up a few of the code within the repository this week, with minor adjustments to make construct/compile steps extra streamlined.
Downloads for these payloads are on the github web page right here.
Libhijacker updates, Sistr0 on the case
Late final week Astrelsky launched libhijacker, a mechanism to run separate processes (Homebrew) on a hacked PS5. Since then, a number of hackers have been taking curiosity within the code. Sistr0 specifically created a fork of the repository, including Linux/clang 12 compatibility.
Astrelsky on his finish has been pushing some updates to his repo, notably including extra logs, and enhanced library assist (stubs) for PS5 Homebrew.
Hopefully these adjustments get merged ultimately for some unified goodness.
Downloads for the libhijacker software could be discovered right here:
A private observe: if you happen to’re like me on a decrease firmware (1.xx or 2.xx), I do know it may be very irritating to see all these updates that you just don’t get to take pleasure in (the exploits being on 3.xx and 4.xx). But the final consensus from hackers is that 1.xx and a couple of.xx are extraordinarily worthwhile firmwares (they do have vulnerabilities and it’s believed their model of the hypervisor isn’t as rock strong as more moderen iterations), and updating these may be a horrible resolution.
