PS5Dev/Byepervisor-Reborn
Somehow, Byepervisor returned...
Older snapshot: check the original source for current information.
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
Note: This repo should be considered a base exploit for work to be built on top of. It is not useful to regular users in its current release state, this is intended for developers. PS5 hypervisor exploit for 6.xx - 13.60 firmware. Bug details can be found here. This bug was initially found by theflow0 and subsequently more people recently w/ assistance of LLMs. The TLDR is that on S3 resume, the startupmp hypercall is invoked on core 0 to initialize the other AP cores (1-15), and takes a reset vector (rip) as one of the arguments for where the core will execute from. During this time on cores 1-15, an insecure Nested Page Table (NPT) config is applied. We can abuse this to run some shellcode that has R/W into the hypervisor's address space including the VM Control Blocks (VMCBs). Very similarly to (one version of) byepervisor of old,…
Read the full README ↗ · Preview checked 2026-10-28T05:22:52.096Z
Inside the original README — Document outline
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
What this repository does
Somehow, Byepervisor returned...
Repository facts
- Owner
- PS5Dev
- Primary language
- C
- Stars
- 486
- Forks
- 104
- Open issues + pull requests
- 20
- License
- Not reported — inspect the license file
- Archived
- No
- Default branch
- main
- Created
- 2026-10-12T22:26:34.000Z
- Last push
- 2026-10-12T22:52:46.000Z
Topics and intended use
No topics were included in the latest source metadata.
Review the README for scope, installation, examples and limitations. We do not run repository code or certify it.
Evaluate before installing
Review licensing and dependencies, inspect recent commits and unresolved issues, and test in an isolated environment before production use. Stars and forks alone cannot answer these questions.
Source and freshness
Source: GitHub. Metadata observed 2026-10-19T12:10:32.749Z. Daily imports are snapshots, not real-time monitoring.
Popularity and source listings do not establish security, suitability, licensing rights or benchmark performance.