Archknight & Yuki Mirahiru retweeted
github.com/ACD421/PHP Sooooo many vulns
@J4ck3LSyN @Archknight23
This is a credit theft attempt dressed up as process.
I found the bug. I put the work on a public GitHub. PHP security wrote me back and @IlijaTovilo admitted the PoC is based on my finding.
Then he said the person who refiled it through security@ / GHSA "will get the credit … because that's how it works."
That is a lie about CVE rules.
CVE CNA Operational Rules §5.2.4: credits are optional (MAY). Nothing says the inbox refiler gets finder credit and the person who identified the vulnerability is erased.
The CVE Record Format separates finder (identifies the vulnerability) from reporter (notifies the vendor/CNA). Those are different roles.
CVE-2026-115560 is still Reserved. The record is not published yet. They are deciding credit now, in email, against their own admission.
Same thread, he accused me of "potentially 0-daying the entire world" and "giving the recipe to every person on the planet." Then he moves to strip finder credit from the person whose work he just admitted using.
Video is the full chain. Watch it. Do not take my word. Take theirs. We won't get credit. We won't get thanked. We won't get paid. PHP has been lying to you all and its time we hold them accountable. Stop using PHP. Find something new. Get rid of tech debt and bad security teams.
@WIRED @TechCrunch @DarkReading @SecurityWeek @motherboard @KimZetter @josephmenn @MITREcorp @TheRecord_Media @IlijaTovilo @ThePHPF @official_php @CVEnew @CISAgov @TheHackersNews @arstechnica @briankrebs @BleepinComputer @troyhunt @SwiftOnSecurity @campuscodi @TheRegister @Girgias
#CVE #CVE2026115560 #PHP #PHPsec #OffSec #FullDisclosure #PublicDisclosure #HackThePlanet #BugBounty #InfoSec #CyberSecurity #SecurityResearch #CreditWhereItsDue #OpenSourceSecurity #GitHub
Archknight & Yuki Mirahiru retweeted
threat-intelligence.redeyese…
@acd421 dropped it hot
Archknight & Yuki Mirahiru retweeted
これめっちゃ便利や!!
SFX(効果音)をコードで作るためのOSS【earshot】
ElevenlabsとかSunoとか課金せずにコードだけで作れるから、めっちゃAIモーショングラフィックスとめっちゃ相性いいわ。
私もEarshot使って作った音でモーショングラフィックスのデモを作ったから見て。
この動画全てコードからできてる…Oh...デジタルネイチャ...
↓↓↓↓↓
earshot v0.4 is out!
added:
- 51 new sounds, all made with code (252 now)
- cut hits, knocks, drips, shutters, chimes, UI pops and reverse swells and more
- a new launch kit: so the sounds will be right on the cut and above the music
+ a website where you can play every single sound
>> leonxlnx.github.io/earshot-s…
all the sfx in this video are made with earshot :)
Archknight & Yuki Mirahiru retweeted
新しい歌声合成ソフトを公開しました! インストール、GPU不要で、あなたのCPUとブラウザで軽快に動作するフル機能のSVSです(Chrome推奨)。ページにアクセスしてすぐ使えるので、ぜひ触ってみてください。
wavtechyukky.github.io/vocat…
Archknight & Yuki Mirahiru retweeted
Free game release! Play Slay the Size, a giantess deckbuilding roguelike where size changes everything.
Download: patreon.com/GtsNae/posts/bon…
❤️ Supporters can unlock bonus characters!
#Roguelike #Deckbuilding #Gts #SizeTwitter #Giantess #IndieGameDev
Verifying the CoinGecko community-takeover + info update for PHP-UP-2026 ($PHP).
Request ID: CU2310260004
GeckoTerminal: geckoterminal.com/solana/tok…
Contract: Cbkg5w7V7W2J2sUmecnyN825CbvwvXwasfhduVtNpump
Now community-run as a security-research tip jar. jackalsyn.com
Archknight & Yuki Mirahiru retweeted
introducing tsubi.club
a new home base. four years in the making.
Archknight & Yuki Mirahiru retweeted
Vtuberたちにわかりやすく言っておくと、いま配信すると配信しているPCが乗っ取られる可能性があります。チャンネルも乗っ取られる可能性があります。あと、あなたの履歴が漏洩します。
「うーわ清楚な顔してコイツ犯され系見てるわきっしょw」とか
「5分前こんな動画みてたんだね♡発情期のメスかよw」とか
置き手紙されたりします。気をつけてください。
(大手ハッキング事例より
【OBSを使ってる活動者さんへ】
ネットであたふたしているPHP問題
OBS自体に影響はないですが↓
OBSのソースにブラウザを追加している場合、念のため注意が必要です。
ソースで追加したブラウザがPHPである場合、OBSのブラウザソースのぺージ権限が”OBSへの高度なアクセス(シーンの変更、リプレイバッファの開始/停止など。)"以上になっている場合は、リンクしたウェブサイト経由でOBSを外部からカスタマイズ、配信等できてしまいます。
なので自身のOBSのソースからブラウザのプロパティでページ権限の確認をおすすめします。
初期設定は”OBSへのアクセス権無し”になっていると思いますが何かの理由で変更してしまっている可能性もあるので確認をっ!
みんなデスドルノートとかいうクソ二流ゴシップアカウントに騙されて @J4ck3LSyN を総攻撃してるのヤバい
この人は確かにモラルには欠けていたかもしれないけど、今回の PHP 騒動の直接的な原因でも諸悪の根源でもないよ……
本当に害悪度 SSS+ なのは誤情報を平気で流してるデスドルノート本人だろ
【害悪度SSS+】
研究者
JAckAi @J4ck3LSyN
備考 : 脆弱性の内容を公開 (諸悪の根源)
※2枚目はわかりやすく説明
Archknight & Yuki Mirahiru retweeted
ok so I've been vibe coding a lot lately, mostly just learning and breaking stuff
then PHP2Shell dropped yesterday, saw how bad it was and thought "wait, I can actually build something useful for this"
so I did. took me like 4h
1/
it's called PHPeek, a tiny browser extension
you open a site and the icon tells you if it's running a PHP version exposed to PHP2Shell:
🔴 likely exposed
🟢 patched
🟠 runs PHP but hides the version
that's it. one glance
2/
made it fully open source bc a security tool you can't read is kinda sus lol
it doesn't send anything anywhere, no tracking, no data. just reads headers your browser already has. <200 lines, go read them
github.com/phpeek-ext/phpeek
3/
submitted to Firefox + Chrome Web Store tonight, both in review rn 🤞
not gonna pretend I'm some security expert, I just thought this was useful and wanted to ship it instead of sitting on it
feedback, bugs, roasts all welcome 🫡
Call me paranoid, but be extra careful visiting ANY web site in the next few days, as some web admins are not always up-to-date with security patches.
Two vulnerabilities (CVE-2026-109618 and CVE-2026-109619) reported for PHP, the web programming language, affecting servers running popular apps like WordPress and Magento, with patches released October 21, 2026 after details leaked early.
Exploitation was confirmed in the wild soon after disclosure, prompting quick WAF protections and patching by IT teams, as unauthenticated attacks could turn visited sites into vectors for credential theft or device exploits.
Stay SAFU!
Archknight & Yuki Mirahiru retweeted
Replying to @kohsai_m @J4ck3LSyN
I have a question, who the fuck made you the moral authority, judge jury or executioner?
If you'd like to take it up with anyone, perhaps read that PHP has no warranty expressed or implied.
Newer releases (BSD 3-Clause): PHP has completed its move to the BSD 3-Clause license and retired PHP License 3.01. BSD-3-Clause carries the same kind of disclaimer: provided as is, no warranties, no liability for damages. The change was voted on through April 4, 2026. The RFC originally targeted PHP 9.0, then was changed to apply to the “next version” of PHP, so which license applies depends on the release. Code published under a given license version can continue to be used under that version. To be sure, check the LICENSE file in the exact branch or tag you’re looking at.
AND
PHP is provided with no warranty, and the license says so explicitly.
Older releases (PHP License 3.01): The license says the software is provided by the PHP development team “as is,” with all express or implied warranties disclaimed, including merchantability and fitness for a particular purpose. It also says the PHP team and its contributors aren’t liable for any direct, indirect, incidental, special, exemplary, or consequential damages, whatever the legal theory, including negligence, even if they were warned of the possibility.
The criminals are the moronic assholes who built a system so insecure in the first place, that a kid in his bedroom could make it hiccup with a few web requests.
Don't hate the messengers. ;)
Meow.




























