- Android ps4 exploit host
- Linux, macOS, Windows, ARM, and containers
- Matrix builds
- Any language
- Live logs
- Built-in secret store
- Multi-container testing
- v0.4.6RC2
- Assets
- v0.4.6a1
- Assets
- Assets
- Assets
- — ARM Build/RPi Scripts coming by this weekend
- Assets
- UPDATED FOR 5.05
- Changelog
- Announcement
- android ps4 exploit host v1.4.3
- Assets
- Assets
- android ps4 exploit host v1.4.1
- Assets
- android ps4 exploit host v1.4.0
- Assets
- android ps4 exploit host v1.3.9
- Assets
- android ps4 exploit host v1.3.8
- Assets
- android ps4 exploit host v1.3.7
- Assets
- android ps4 exploit host v1.3.6
- Assets
- android ps4 exploit host v1.3.2
- Assets
- 6.72 android ps4 exploit host v1.3.0
- Assets
- Android ps4 exploit host
- Linux, macOS, Windows, ARM, and containers
- Matrix builds
- Any language
- Live logs
- Built-in secret store
- Multi-container testing
- Android ps4 exploit host
Android ps4 exploit host
Automate your workflow from idea to production
GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub.
Linux, macOS, Windows, ARM, and containers
Hosted runners for every major OS make it easy to build and test all your projects. Run directly on a VM or inside a container. Use your own VMs, in the cloud or on-prem, with self-hosted runners.
Matrix builds
Save time with matrix workflows that simultaneously test across multiple operating systems and versions of your runtime.
Any language
GitHub Actions supports Node.js, Python, Java, Ruby, PHP, Go, Rust, .NET, and more. Build, test, and deploy applications in your language of choice.
Live logs
See your workflow run in realtime with color and emoji. It’s one click to copy a link that highlights a specific line number to share a CI/CD failure.
Built-in secret store
Automate your software development practices with workflow files embracing the Git flow by codifying it in your repository.
Multi-container testing
Test your web service and its DB in your workflow by simply adding some docker-compose to your workflow file.
Источник
v0.4.6RC2
No exploits included. Currently working on rebuilding all the payloads.
Assets
v0.4.6a1
Various minor bugfixes
Various caching fixes and optimizations
- Theme cached by default
- Loading bar and notifications for caching
- Exploits cached on demand (By individual firmware or all)
- Caching buttons will not show up offline
- Fixed payload listening exploits while cached
- Preview for «Sticky Caching»
Default theme QoL improvements
- Fixed grey artifacts on buttons
- «O» will now go back
- If only one firmware is available it will autoselect
Added option gzip compression (Enable it in setting)
Settings (Your old settings will not work)
- More/better warning/import rules
- Reorganized
- UA_Check disabled by default
- Added DNS settings (Changing the port will not just work, if you change it you’re on your own)
- Add default timeout for payload sender
- Add gzip compression level (Valid values are 0 through 9, from least to most compression, 0 is disabled)
You can now specify a payload to send from the exploit itself
Copy the «Original» exploit, in «index.html» change ping(«/success»); to ping(«/success/9020/15/test.bin); to send «test.bin» (from the payloads folder) to port 9020 after successful exploitation with a 15 second timeout
UA blocker now uses regex
Updated Readme and FAQ
App2USB rebuilt for release
Assets
- Fixed issue with cache manifest generation
- Added hash to manifest
Assets
- Whitespace issue fixed #113
- Added offline HTML5 cache option to settings (Enabled by default) by @ps4miner#108
Nuked because it was not always caching, use 0.4.5 instead
Assets
- 5.05/5.07 enabled by default
- 5.05 payloads/exploits included
- Fixed network test
- Fixed updater
- RPi issue fixed by @Vadammt
- Removed 4.05 spoofed UA in settings.json and default theme’s script.js (Even less reason to be on 4.05 now)
- Block all Nintendo subdomains
— ARM Build/RPi Scripts coming by this weekend
Assets
UPDATED FOR 5.05
Last change at 4:30am UTC on May 28th
Changelog
- Javascript/OSX Error fix by @alu0100845235
- Switched #!/usr/bin/python3 back to #!/usr/bin/env python3 by @artik
- auto_exploit fix by @MoserB
- Added HTTP_Port and Root_Check setting by @arioko
- Added version in menu header by @arioko
- Renamed Interface setting to Interface_IP requested by @JanJastrow
- Added —settings arg to specify settings.json file location requested by xeroxmalf#7646
- Updated README.md
- Added FAQ.md
- Add Host_Version into data javascript object to use in themes
- Add Lang_Code into data javascript object, if available, to use in themes
- Attempt to detect spoofer with default theme (New included HEN uses 5.51 spoofer. since 5.51 doesn’t exist, yet, it’s mapped to 4.55, likewise 5.05 is mapped to 4.05 as the full UA for 5.05 is blocked by default so if 5.05 is able to access the page it’s actually 4.05, be aware 4.05 support is dropped)
- Fixed issue with menu not reopening after selecting «Don’t send a payload»
- Renamed DNS_Rules[‘Pass_Through’] setting to DNS_Rules[‘Pass_Through_IP’]
- Renamed DNS_Rules[‘Self’] setting to DNS_Rules[‘Redirect’]
- Added DNS_Rules[‘Redirect_IP’] to settings
- Removed warning on empty setting, the default, for Interface_IP
- Remove unused patch payload function
- Updated/Added payloads
- Removed majority of 4.05 payloads from release
- Add alias for URL http://the.gate while using DNS (Project likely being renamed due to the next bullets in this list and the announcement)
- Nintendo Switch (3.0.0) support (Mostly Untested)
- Block Updates with DNS
- Redirect connection test
- No exploit included (nx-hbexploit in next release)
- PlayStation Vita (3.60) Support (Mostly Untested)
- Blocks updates with DNS
- Redirect User’s Manual
- Updater support
- No exploit included (Henkaku in next release)
- More console support pending
- Removed some update settings. I’ll build a standalone update deleter or something
- THE UPDATER NO LONGER CHECKS MD5 CHECKSUMS
Announcement
This project has been a little neglected since the 0.4.1 release almost a month ago as I’ve been working on another project since that release. I’ve haven’t been hiding and posted a bit on Discord so this won’t come as a surprise to some. It’s a «modchip» for webkit exploits, mirroring the existing ESP8266 methods, just with more features/polish. The device can either create a network to connect to (No internet access), connect to an existing network (Works just like this host), or create a bridge (Enabling internet access though the device). It’s a custom PCB that’s about 25mm*18mm*4mm (Currently) so it should fit inside most consoles. The front end looks like my regular exploit host and you can view a demo (out of date) of the control panel here.
Features
- Control the device from your phone/computer over Bluetooth/Wifi
- Open API for developers to interact/control the device
- Press physical buttons on the console
- View/Download UART data
- Add, download, or delete exploits with one button click
- Custom filetype (Compresses exploits into a single file to install/share)
- Supports both Bin and JS payloads
- Includes application to compress/extract these files
- This is to save space and add to ease of use
- Web based firmware updates for this device (Need no physical access to device to update it)
- Basic usage without soldering (No buttons or UART)
- A secret feature that’ll be revealed after it’s working 100%
- If you do some snooping on the PCB you might be able to guess it
Hardware Info
- USB-C port (Custom pinout for internal installation, but can just run off USB power)
- SD card for exploit storage (GBs vs 3MB)
- User Expandable
- Custom Case for external use (Extender to turn a female USB-C to a male USB-A)
Testing process
- Software testing with ESP(8266/32) dev boards.
- Finish prototype PCB boards.
- Send out prototype boards. Will be a small batch, about 10 boards.
- «Finish» software, get feedback, make revisions to PCB as necessary.
- First batch of v1.0 boards. (Current bill of materials puts PCB cost @ $10 depending on interest, larger order sizes will make the board cheaper)
Beta Tester Info
It’s currently in a working state, just using the API, with majority of the features are done (Currently the bluetooth controller & the admin panel HTML+JS are not 100%) and I’ll be looking for testers (Bring your own board) within the next two week or so. Contact me on Twitter or Discord if your interested in testing.
To be a part of the first testing process you just need familiarity with the exploit process and familiarity with your ESP board (Be able to use the serial logger and flash the firmware).
To get one of the prototype boards soldering ability is a must. There are
6 wires to solder, 2 of which being on the PS4 motherboard. I’ll eat the cost for the prototypes.
If there is demand for prototypes, I may make a bigger order and will send them out at cost or make a bigger PCB order and send out PCBs with the bill of materials.
When all is said and done I plan to open source all the code/PCB info so others can help further development/produce boards for others. I want to have it at a 1.0 state before releasing before having others make incompatible software/PCBs.
Источник
android ps4 exploit host v1.4.3
Assets
- support of 7.50, 7.51, 7.55
- updated wolf menu
- updated hakkuraifu menu
- removed leeful 6.72 versions and kept the v10 (most stable one). if you want the old ones download older version of this app
- changed simple menu to kids menu
- added support of 7.50, 7.51, 7.55 to kids menu (needs testing as i dont have these firmwares to test)
Assets
android ps4 exploit host v1.4.1
- Updated The wolf menu to the latest version.
Assets
android ps4 exploit host v1.4.0
- Added hakkuraifu exploit menu that includes 7.02 (needs testing as i don’t have 7.02).
Assets
android ps4 exploit host v1.3.9
- Added Leeful Menu v10
- Updated Wolf Menu
Assets
android ps4 exploit host v1.3.8
fixed some payloads won’t cache in leeful’s v8
updated wolf menu
added new menu (PS4). still experimental and a little bit laggy.
(Credit for https://codepen.io/Pixmy/pen/qaYQoV) for the theme core code
Assets
android ps4 exploit host v1.3.7
-updated wolf’s game menu
Assets
android ps4 exploit host v1.3.6
- Added Leeful menu v7 & v8 combined (same with difference Hen v2.1.3b)
- Added Wolf Games menu 5.05 & 6.72
- increased performance for menus and themes.
(didn’t test everything. if errors found please do tell)
Assets
android ps4 exploit host v1.3.2
- added leeful 5.05 v6.5 exploit menu (need testing cuz i dont have 5.05 PS4)
- now display is always on when using the app.
- cleaned some code, better performance.
- some UI fixes.
Assets
6.72 android ps4 exploit host v1.3.0
- Fixed hotspot issues for some devices.
- fixed not being able to install in some devices (hope will cover most with no issues)
- added payload sender support (top right corner click on 3 dots)
Assets
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Android ps4 exploit host
Automate your workflow from idea to production
GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub.
Linux, macOS, Windows, ARM, and containers
Hosted runners for every major OS make it easy to build and test all your projects. Run directly on a VM or inside a container. Use your own VMs, in the cloud or on-prem, with self-hosted runners.
Matrix builds
Save time with matrix workflows that simultaneously test across multiple operating systems and versions of your runtime.
Any language
GitHub Actions supports Node.js, Python, Java, Ruby, PHP, Go, Rust, .NET, and more. Build, test, and deploy applications in your language of choice.
Live logs
See your workflow run in realtime with color and emoji. It’s one click to copy a link that highlights a specific line number to share a CI/CD failure.
Built-in secret store
Automate your software development practices with workflow files embracing the Git flow by codifying it in your repository.
Multi-container testing
Test your web service and its DB in your workflow by simply adding some docker-compose to your workflow file.
Источник
Android ps4 exploit host
PS4 Exploit Host
This is an easy way for anyone to host their own exploit for the PS4 on their LAN. Features include:
- Hosts your choice of exploit
- Allows caching of exploits for offline use
- Sends your choice of payload after a successful exploit
- Blocks PSN domains from resolving (Stops accidental updates and block telemetry)
- Serves a specific firmware update to your PS4
- Works on just about every platform
- Static Website builder, to run on HTTP server of your choice (You lose some features using this method, DNS, updater, etc)
If you do not want to host the package yourself you can use my remote DNS. See the Using remote DNS section below.
PLEASE READ THIS README AND THE FAQ BEFORE POSTING AN ISSUE.
- If you are not using a binary release you will need Python 3
- Root privileges on non-Windows machines
How to download
Download the zip on the releases page
Download with Git, be sure to grab the submodules. This does not include any exploits or payloads. This is for experts only, download a release if you have issues
git clone —recursive https://github.com/Al-Azif/ps4-exploit-host.git
Using remote DNS (Run Nothing Locally)
- Make sure the PS4 is on firmware 7.02 or lower ( Settings > System > System Information ).
- If your firmware version is >7.02 you are out of luck there is no public exploit available and you cannot downgrade.
- On your PS4 go to Settings > Network > Setup Network to setup a network. When you get to DNS Settings select Manual and set the Primary to 165.227.83.145 and the Secondary DNS to 192.241.221.79 or visa-versa.
- If your firmware version is Settings > User’s Guide and select it. The exploit selection should appear.
- You can also open browser and the default homepage will be the exploit selection.
- If you use Bin Loader you will need to use another program to send a payload.
- If your firmware version is Settings > User’s Guide and select it. The exploit selection should appear.
My Twitter is @_AlAzif you can check my recent tweets for know issues/maintenance info
How to run (Run Locally)
- Download the files (As shown in the «How to download» section above)
- Double click the executable ( ps4-exploit-host.exe , start.py , etc). If it starts with no errors, note the IP given
- Alternatively run it from the command line ( ps4-exploit-host.exe , ./ps4-exploit-host , python start.py , etc)
- If you are not root when running on a non-Windows machine you need to use sudo
- On your PS4 Settings > Network > Setup Network to setup a network. When you get to DNS Settings select Manual and set the Primary and Secondary DNS to the IP address you noted above.
- Make sure the PS4 is on a firmware version Settings > System > System Information ).
- If your firmware version is >7.02 you are out of luck there is no public exploit available and you cannot downgrade.
- On the PS4, go to Settings > User’s Guide and select it. The exploit should run and there should be output on the script window. (Alternatively you can just open the Browser)
- If applicable for your chosen exploit, the script will prompt you to choose a payload to send. You may send any payload located in the payloads folder.
- When done use Ctrl+C to cleanly close the application
Note: You can edit settings.json to modify the hosts behavior. There is a section below with more info.
Running on Raspberry Pi
While the «How to run» section applies to the Pi as well there are some more complex options people may want to use for the Pi like running without any network whatsoever.
- To run as a standalone device that you plug directly into your device though ethernet go here (Supports any Pi with a ethernet port)
- To run as a WiFi access point for your device go here (Officially supports RPi 3 currently, may work on others with WiFi adapter)
How to use the built in updater
If you already have an official updated above 5.05 downloaded you must delete it first.
Follow the «How to run» section until it says to come here
Put the system update in the updates folder as PS4UPDATE_SYSTEM.PUP
Optionally put the recovery update in the updates folder as PS4UPDATE_RECOVERY.PUP
5.05 SYS MD5: F86D4F9D2C049547BD61F942151FFB55
5.05 REC MD5: C2A602174F6B1D8EF599640CD276924A
MAKE SURE THE DNS IS SET CORRECTLY!
SEE #2 I’M SO SERIOUS!
There should be a different page on the System Software Update > View Details option on the PS4. It will be obvious!
- The PS4 is not using the right DNS if you get the standard Sony changelog page. STOP IMMEDIATELY AND RESTART THE ENTIRE PROCESS
Run a system update on your PS4 system.
Return to the «How to run» section
It’s probably a good idea to make a backup of the default settings.json just in case. Any invalid settings will throw a warning and use a default value.
Use valid json formatting. Boolean values should be lower case, integers should not be quoted, etc.
Setting | Notes | Type |
---|---|---|
Debug | Will print debug info from the DNS/HTTP servers | boolean |
Root_Check | Will skip the root user check for Linux/OSX, only disable if you are sure you don’t need it. Will cause port errors if set wrong | boolean |
Public | If the server is listening on a public IP (Disabled payload sending other than «Auto_Payload and disables viewing/editing settings remotely) | boolean |
DNS | If the DNS server should be run | boolean |
HTTP | If the HTTP server should be run | boolean |
DNS_Interface | The IP of the interface to bind the DNS server to | string (IP Address) |
DNS_Port | The port to bind the DNS server to | int (1-65535) |
HTTP_Interface | The IP of the interface to bind the HTTP server to | string (IP Address) |
HTTP_Port | The port to bind the HTTP server to | int (1-65535) |
Compression_Level | Enables gzip compression on the HTTP server, 0 being disabled, 9 being most compressed | int (0-9) |
UA_Check | If the UA should be checked against values in the Valid_UA setting | boolean |
Theme | Which theme to use, themes must be located in the themes folder | string |
Sticky_Cache | Whether the appcache manifest should be included in itself or not | boolean |
Auto_Payload | Payload to send to any IP that accesses server at /success . Payload must be in the payloads folder | string |
Payload_Timeout | The timeout, in seconds, to try and send a payload through the payload menu before timing out | int (1-999) |
DNS_Rules | Fake DNS control block | |
DNS_Rules [Redirect IP] | The IP address to redirect URLs listed in the Redirect rules to | string (IP Address) |
DNS_Rules [Redirect] | Array of domains to forwards to DNS_Rules [Redirect IP] | array of strings (regex) |
DNS_Rules [Block] | Array of domains to block | array of strings (regex) |
DNS_Rules [Pass_Through] | Array of IP addresses to not modify DNS requests | array of strings (IP Address) |
Valid_UA | User-Agents to allow access to exploits, only used if UA_Check is enabled | array of strings (regex) |
Update | Updater control block | |
Update [PS4_No_Update] | The PS4 version (and lower) listed here will not be served update files | float |
Update [Vita_No_Update] | The PS Vita version (and lower) listed here will not be served update files | float |
About offline caching
- Redirect/Theme info is cached automatically
- Redirect/Theme info updates and refreshes automatically
- Exploits can be cached on a per firmware basis or all cached at once with the dropdown menu and/or [Cache All] button on the exploit selection menu.
- Exploit updates must be «manually» updated by clicking cache button an update is available or checking the «About» option in the exploit’s dropdown menu.
- You will be told if there is no update when clicking the button.
- If you are offline the caching buttons will be hidden as will exploits that require a network connection or are not cached
- Exploits can be automatically selected by clicking «Autoload» in the exploits dropdown menu
- When you open the browser it’ll automatically select that exploit
- This can be disabled by clearing your browsers cookies
You can check the issue tracker for my to do list and/or bugs. Feel free to send a pull request for whatever. Be sure to report any bugs, include as much information as possible.
What if a new exploit is released?
You should just be able to place the exploit files in the exploit directory. The exploit will automatically add the exploit to the menu.
Why do you commit so many little changes, tweaks, etc?
I have no self control. it also lets people see the actual development. From barely working chicken scratch to actual code.
Источник