provavelmente devo voltar fazer bug bounty só ano q vem agora, ainda tem alguns reports pra receber mas agora é aproveitar o tempo pra estudar mais fundo algumas coisas
e em breve tbm to pensando em começar a criar alguns videos diferentes pro yt sobre infosec e bug bounty
Replying to @thegrugq
Fear of 0day is like being terrified of ninjas instead of cardiovascular disease.
sy.br1d retweeted
‼️ UPDATE - Tailscale confirms the Tailworm SSH flaws are real.
Its new investigation page says most of what it found is privilege escalation and calls the issues “serious.” Fix targeted within 24 hours — no CVE or patched version out yet.
Mitigate now:
→ Set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service and restart
→ Tighten SSH access rules to the users/devices that need them
Read: thehackernews.com/2026/10/un…
i know most of everyone’s focus is on the php bugs but this one is really important to patch quickly too!!
this same brotli vulnerability impacts a bunch of things, including express.js on node or bun with an app.use(express.json()) or the cURL client with the --compressed flag.
super proud of @k_tr4n and the rest of our team who helped find and disclose this!
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
patchtheplanet.org/brotli
sy.br1d retweeted
PHPの助弱性で日本にサーバー攻撃が集中…
分かりやすく言うとサマーウォーズ状態。
Readers added context they thought people might want to know
PHPの脆弱性は世界中のPHPサーバーに影響し、攻撃が日本に集中しているという事実は確認されていない。BBC報道などでは世界各国で同様の予防対応が見られる。
bbc.com/news/articles/…
php.net
japancyberwatch.com/articles/php2s…
sy.br1d retweeted
To teach a lesson,
After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought phpbleed.com before wiz could pull the same stunt again.
A big budget can buy a domain. It shouldn't buy someone else's research credit.
If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve.
Hack the planet. Credit the researchers.
sy.br1d retweeted
皆様に、今夜に対応して頂きたい大至急のお願いです。
多くのウェブサイトで使用されているPHPに関し、PHPのセキュリティチームが、重大な2件の脆弱性に関する注意喚起を行っています。
公開しているウェブサイトでPHPを使用しているか確認し、今夜、10月21日午後11時(日本時間)に公開される修正パッチについて、可及的速やかに適用できるよう準備をお願いします。
修正パッチを速やかに適用することが困難な場合は、例えばウェブサイト等を一時的に停止させることも、リスクを低減させるための有効策の一つと考えられます。
国家サイバー統括室のXアカウントでも関係する情報を発信していますので、そちらも参考にして下さい。
国家サイバー統括室(注意・警戒情報)(@cyber_forecast) / X























