NOSLOP

NOSLOP is a single-page PS5 research controller with a local kernel-audit ledger.

Scope

• FW 13.60 has an exact userland gate and accepts only a verified provider.
• FTP ROP controls are isolated to FW 9.00, 9.20, 9.40, 9.60, 10.00, and 10.01.
• No PS5 13.60 kernel offsets, kernel exploit, ELF loader, or remote JavaScript loader is bundled.
• Payloads are local and allowlisted by payloads/manifest.json.
• SPRX dumping is bounded to 64 MiB, sequential, and requires verified module metadata.
• The PS4 11.52 kernel material is a local static audit ledger only. It contains no runnable kernel test.
• The audit verdict is negative for a validated useful memory-corruption primitive and does not establish PS5 transferability.

The offset entries are unverified local candidates, not hardware proof. The provider interface in exploit.js is the deliberate boundary for a separately verified runtime. No remote repository content or remote loader is used by this tree.

Serve

node tools/serve.js --host 0.0.0.0 --port 8080

Open http://<host>:8080/ on the console. Dump output is written below corpus/dumps/ or the directory named by NOSLOP_DUMP_ROOT.

The local server accepts only the sequential dump protocol. It does not provide payload injection, ELF launch, or a kernel endpoint.

Provider Interface

The page does not infer success from an offset table. A separately verified provider may set window.NOSLOP_USERLAND_PROVIDER before exploit.js runs:

{
  firmware: "13.60",
  verified: true,
  read(address, length) { /* return Uint8Array */ },
  modules: {
    "libSceNKWebKit.sprx": {
      base: 0x800000000,
      loadBias: 0x800000000,
      programHeaderAddress: 0x800000040,
      imageSize: 0x1000
    }
    }
}

The example values are shape-only. They are not supplied offsets or proof.

Kernel Audit

research/ps4-11.52-audit.json and research/ps4-11.52-kernel-audit.md record the supplied PS4 11.52 static findings. The page displays the four primary leads and their validation gates, but it never executes them. A matching PS5 image, target-specific proof, and authorized runtime environment are required before any PS5 kernel conclusion can be made.