PS5 Hack news: libhijacker updates, compiled BD-JB SDK Payloads
In PS5 hacking news this week, compiled payloads for people running BD-JB and some updates on libhijacker, the PS5 Homebrew “library”.
BD-JB Payloads Compiled
PS5 scene developer John Tornblom has released a compiled version of the payloads he maintains with his BD-JB PS5 SDK. The payloads are various pieces of executable code you can run on a PS5 after triggering the BD-JB exploit (to my knowledge these are not compatible with the Webkit exploit at the moment, although that could change eventually if the webkit version of the kernel exploit gets updated).
These payloads are not new, but those of us who were tired to look for compiled versions in random corners of the internet will be happy to find them directly at the source. These payloads include an elf loader, various samples to test the SDK (hello world, sprx loading, arbitrary syscall execution, etc…), a kernel dumper, Hardware info (CPU Temperature, Frequency, etc…), and more. (Notably, no FTP server in there).
John has also used the opportunity to clean up some of the code in the repository this week, with minor changes to make build/compile steps more streamlined.
Downloads for these payloads are on the github page here.
Libhijacker updates, Sistr0 on the case
Late last week Astrelsky released libhijacker, a mechanism to run separate processes (Homebrew) on a hacked PS5. Since then, several hackers have been taking interest in the code. Sistr0 in particular created a fork of the repository, adding Linux/clang 12 compatibility.
Astrelsky on his end has been pushing some updates to his repo, notably adding more logs, and enhanced library support (stubs) for PS5 Homebrew.
Hopefully these changes get merged eventually for some unified goodness.
Downloads for the libhijacker tool can be found here:
A personal note: if you’re like me on a lower firmware (1.xx or 2.xx), I know it can be very frustrating to see all these updates that you don’t get to enjoy (the exploits being on 3.xx and 4.xx). But the general consensus from hackers is that 1.xx and 2.xx are extremely valuable firmwares (they do have vulnerabilities and it is believed their version of the hypervisor isn’t as rock solid as more recent iterations), and updating those might be a terrible decision.