CURRENT MISSION: Conclude the 2026 soyjak.party hack page, aswell as any pages relating to it, such as the Summer 2026 Crisis page.
Update Quotecord with any relevant info. See the blackboard for more info.
2026 soyjak.party hack
Check again later for more coverage.
On August 11, 2026, at 6:11 AM UTC, a Shiwi user under the name of Zhambyl Tulegbenpenov would claim that the reason behind the 2026 outage and subsequent Second Great Handover was because soyjak.party was hacked and had its source code stolen. [1] In his post, he stated that he hated niggers, trannies, and Jews and then linked the leak in a gofile link. The link contains a 2.6GB file named "vichan.zip" which contains the Sharty's Vichan fork along with some Telegram channel export. Later that day at 3:02 PM UTC, another Kiwi Farms user under the name Femtanyl (who was also responsible for the 'ru source code leak) later claimed that the hack was done by a Soycord of failtrolls and that the hacker(s) had exploited an RCE[a] vulnerability within Quote's MPA system.[2] That is to say they uploaded a malicious executor of some kind to the server via the MPA system, similar to how 4cuck was hacked.
Pre-leak
The hack was allegedly done by a Soycord, in which it likely spread around after to other groups and eventually got to Zhambyl. The source code was then kept secret and Quote blamed the downtime on hard drive failures while transferring servers.[3]
Reaction
Reactions have been relatively underwhelming on the Sharty, mainly due the fact that it's been too little time for anyone to realize the extent of how bad this can be. A thread on /soy/ was posted in which users either did not care or made connections to theories of Salt being Quote, leading to the thread being largely ignored.[4] The hackers also didn't try to fuck things up and do a reverse Cuckset... yet.
What's included
- McChallenge (found in "
js/captcha/static") - Secure tripcode salt[b] (changed as of August 13, 2026)
- Banned user agents
- Source code for the 2026 April Fools frontend (found in "
frontend") - Moderation guidelines and a bunch of janny shit
- Discord webhooks
- Hardcoded integrity bans
- (hashed) Admin password
Suspiciously, integrity.js is nowhere to be found in this leak, despite being linked to multiple times. [although it was included in the nuuru leak so you could use that anyway]
IP leak
The next day an alleged .txt of 2000 IP addresses from sharty posters was leaked. 178 IP addresses belonged to the US Department of Defense[c], and some other glowie stuff like 1 place in Turkey, another in Australia and an "Internet Research Organization" in Japan. Also a lot of Chinese and Japanese IP addresses compared to other countries for some reason.[5]|
On August 13, 2026, a security vulnerability was discovered in which the ID hashing algorithm (which utilized user IP addresses as input) was exposed as part of the source code leak. This potentially allowed the retrieval of user IP addresses from ID-enabled threads spanning the period from 2024 to August 13, 2026.[6]
Download
You either have Gofile, Magnet or Torrent.
See also
Notes
- ↑ Remote Code Execution, essentially when someone who doesn't have physical/direct server access is able to execute code on the server side regardless of this.
- ↑ The salt is
OSSL.4lNNPl85dg+m5OmYnDRgy4XmRZYmXYV7wN+1Pwkb9mjGZ8mmyHvoUZVXQvCvrl4FGKVIyWqhpQJu55N4RcW/rZd3wYABmCwd4hENkvQNUWD9d6Zc/k54LUn4q3yqj8ffHGokSh+yUnc/qhusSd/IzVbyBWjVkWmM6+Uf86uPHKU= - ↑ Before any of the schizos start raising hell about how the Defense Intelligence Agency is trying to take over the site, you must understand that ISPs will regularly route traffic between the modem (your endpoint) and the CMTS (your ISPs point) via another address range that does not necessarily belong to them. The DoD owns many 8/ IPv4 blocks owing to the fact that they basically created the internet, ownership of a block being signified by the number at the start of it and what it's assigned to. For example, a /8 IP Block starting with 22 means that it's owned by the Defense Information Systems Agency for the DoD. However, most gov and mil activities happen over secure internal computer networks like JWICS and SIPRNET, leaving literal millions of addresses in this range unassigned to anything. For this reason a lot of ISPs will just pick out something in a DoD block to use for routing, which, in a route check, will show up as a DoD owned address even if it's really just out in no mans land and nothing's being sent to or from a DoD server. It's possible that atleast one of these addresses really were made by someone at the DoD/Military since sometimes they'll access WWW via their own shit but commercial/recreational service is provided to bases by an ISP called Boingo, IDK if they use DoD blocks to route or not.}} - User:JDS1948 <-- Self-admitted Israeli fed btw
Snopes
- ↑ https://megalodon.jp/2026-0812-0013-44/https://kiwifarms.st:443/threads/soyjak-party-the-sharty.145349/post-25216920
- ↑ https://megalodon.jp/2026-0812-0009-09/https://kiwifarms.st:443/threads/soyjak-party-the-sharty.145349/page-5691
- ↑ Special:PermanentLink/458200
- ↑ https://megalodon.jp/2026-0812-0134-22/https://soyjak.st:443/soy/thread/17018764.html
- ↑ https://megalodon.jp/2026-0812-0233-55/https://soyjak.st:443/soy/src/1786461178355u-1.txt
- ↑ https://megalodon.jp/2026-0813-1803-26/https://soyjak.st:443/soy/thread/17068754.html
