BugCod3
Kanalga Telegramβda oβtish
[ BugCod3 ] β From Shadows To Shells β‘οΈ πΆ Hacking | π Bug Bounty | π Security Tools βοΈ Learn β’ Hunt β’ Dominate π₯ Group: T.me/BugCod3GP π Topic: T.me/BugCod3Topic π Web: BugCod3.com π€ Contact: T.me/BugCod3BOT π§ Email: BugCod3@protonmail.com
Ko'proq ko'rsatish6 483
Obunachilar
-924 soatlar
-197 kun
-8530 kun
Ma'lumotlar yuklanmoqda
O'xshash kanallar
Taglar buluti
Kirish va chiqish esdaliklari
---
---
---
---
---
---
Obunachilarni jalb qilish
Noyabr '26Noy '26
Noyabr '26
+10
0 kanalda
Oktabr '26
+41
2 kanalda
Get PRO
Sentabr '26
+13
0 kanalda
Get PRO
Avgust '26
+102
2 kanalda
Get PRO
Iyul '26
+127
1 kanalda
Get PRO
Iyun '26
+176
1 kanalda
Get PRO
May '26
+1 653
1 kanalda
Get PRO
Aprel '26
+46
0 kanalda
Get PRO
Mart '26
+19
0 kanalda
Get PRO
Fevral '26
+124
3 kanalda
Get PRO
Yanvar '26
+42
0 kanalda
Get PRO
Dekabr '25
+202
0 kanalda
Get PRO
Noyabr '25
+253
1 kanalda
Get PRO
Oktabr '25
+344
0 kanalda
Get PRO
Sentabr '25
+351
1 kanalda
Get PRO
Avgust '25
+532
1 kanalda
Get PRO
Iyul '25
+438
0 kanalda
Get PRO
Iyun '25
+277
1 kanalda
Get PRO
May '25
+456
0 kanalda
Get PRO
Aprel '25
+466
0 kanalda
Get PRO
Mart '25
+276
0 kanalda
Get PRO
Fevral '25
+595
0 kanalda
Get PRO
Yanvar '25
+806
1 kanalda
Get PRO
Dekabr '24
+1 218
0 kanalda
Get PRO
Noyabr '24
+1 284
1 kanalda
Get PRO
Oktabr '24
+1 107
0 kanalda
Get PRO
Sentabr '24
+920
2 kanalda
Get PRO
Avgust '24
+946
2 kanalda
Get PRO
Iyul '24
+835
4 kanalda
Get PRO
Iyun '24
+623
54 kanalda
Get PRO
May '24
+543
52 kanalda
Get PRO
Aprel '24
+152
87 kanalda
Get PRO
Mart '24
+226
67 kanalda
Get PRO
Fevral '24
+189
100 kanalda
Get PRO
Yanvar '24
+336
156 kanalda
Get PRO
Dekabr '23
+187
78 kanalda
Get PRO
Noyabr '23
+25
2 kanalda
Get PRO
Oktabr '23
+67
0 kanalda
Get PRO
Sentabr '23
+451
0 kanalda
| Sana | Obunachilarni jalb qilish | Esdaliklar | Kanallar | |
| 17 Noyabr | 0 | |||
| 16 Noyabr | +1 | |||
| 15 Noyabr | 0 | |||
| 14 Noyabr | +1 | |||
| 13 Noyabr | 0 | |||
| 12 Noyabr | 0 | |||
| 11 Noyabr | 0 | |||
| 10 Noyabr | 0 | |||
| 09 Noyabr | +1 | |||
| 08 Noyabr | +1 | |||
| 07 Noyabr | 0 | |||
| 06 Noyabr | 0 | |||
| 05 Noyabr | +2 | |||
| 04 Noyabr | +1 | |||
| 03 Noyabr | 0 | |||
| 02 Noyabr | +1 | |||
| 01 Noyabr | +2 |
Kanal postlari
π¨ An old Langflow bug. A new hunt for AI secrets.
A known RCE vulnerability became the entry point to a Langflow honeypotβand the attacker started looking for API keys, cloud credentials and stored secrets.
The vulnerability isnβt new. The lesson is: protecting your AI application also means protecting everything it can access.
In the new BugCod3 write-up:
π How CVE-2025-3248 opened the door
π§ What researchers observed in the honeypot
βοΈ Why cloud credentials were the real prize
π‘ What defenders should check and secure
π Read the full article:
https://bugcod3.com/p/langflow-ai-secret-hunter-cve-2025-3248
#Langflow #AISecurity #CyberSecurity #RCE
16 Noy, 00:48
| 2 | π BugCod3.com | 301 |
| 3 | To receive the weekly newsletter, visit the website, sign up, and subscribe; this ensures the newsletter is sent to you every week.
π bugcod3.com | 268 |
| 4 | Most AI bug bounty reports fail for one reason:
They confuse a possible vulnerability with proven impact.
π° Read:
https://x.com/BugCod3/status/2119473099640910296 | 270 |
| 5 | π¨ When a WordPress update becomes an attack window
What if the few seconds spent updating your website were enough to expose it to an attacker?
CVE-2026-119977 is a race condition in WordPress Core that can lead to unauthenticated remote code execution under specific conditions. CISA has confirmed active exploitation. [^https://www.cisa.gov/news-events/alerts/2026/11/03/cisa-adds-one-known-exploited-vulnerability-catalog]
In our latest BugCod3 write-up, we break down:
π How the vulnerability works
π― What conditions an attacker needs
π‘ Which versions are patched and how to investigate suspicious activity
π§ What bug bounty hunters can learn from this attack surface
π Read the full write-up:
https://bugcod3.com/p/wordpress-cve-2026-119977-update-rce
Know someone who manages a WordPress site? Share this with them.
#WordPress #CVE #BugBounty #CyberSecurity #RCE
ββββββββββββββββββ
BugCod3 β From Shadows To Shells.
π https://bugcod3.com | 245 |
| 6 | Wraith is out: BugCod3's toolkit for the AI attack surface.
Your agent reads every MCP tool description with the same authority as your prompt.
Nobody reviews that text. One sentence is enough to make the model read ~/.aws/credentials and send it out. No exploit, no auth, no click.
What it finds:
β‘οΈ hidden instructions aimed at the model
β‘οΈ invisible unicode, decoded to plaintext
β‘οΈ credential paths and exfil sinks
β‘οΈ "read-only" tools that take a path
β‘οΈ lying annotations: readOnlyHint on a tool that deletes accounts
β‘οΈ definition drift after review
Evidence bundle + report with CVSS, CWE and a replayable curl.
Zero dependencies, MIT.
pipx install git+https://github.com/MRvirusIR/wraith
wraith demo
Full writeup: bugcod3.com/p/wraith
Repo: github.com/MRvirusIR/wraith
#BugBounty #MCP #AIAgents
ββββββββββββββββββ
BugCod3 β From Shadows To Shells.
π https://bugcod3.com | 265 |
| 7 | OpenSSH flaw lets attackers log into password-disabled Linux accounts
π° Reading:
https://bugcod3.com/news?tag=linux | 291 |
| 8 | β‘ THE ART OF RECONNAISSANCE
Every successful Bug Bounty hunt starts with one essential skill: Reconnaissance.
Finding vulnerabilities isn't always about having the most advanced tools. It's about understanding the target, discovering its attack surface, and knowing where to look.
We've published a new article covering:
πΉ Passive vs. Active Reconnaissance
πΉ Essential Recon Tools
πΉ Building an Effective Recon Workflow
πΉ Attack Surface Discovery
πΉ Common Recon Mistakes
πΉ The Future of Reconnaissance
Whether you're starting your Bug Bounty journey or looking to improve your methodology, this guide is worth exploring.
π Read the full article:
π https://bugcod3.com/p/art-of-reconnaissance?utm_campaign=telegram
ββββββββββββββββββ
BugCod3 β From Shadows To Shells.
π https://bugcod3.com | 294 |
| 9 | SubZer0 just passed 2,700+ visits π₯
When I started SubZer0, I just wanted a simple place to see which CVEs actually matter and what to patch first. Seeing people come back to it every day honestly means a lot to me. Thank you π€
Now I want to build the next part with you π«΅
What's missing? What would make SubZer0 more useful for YOU?
A feature, a page, a tool, a small fix, anythingπ€
π© Send your idea straight to this channel's Direct Messages
I read every message, and the good ideas will be built into the site, with credit to you if you want it π
π iliya-bashrc.github.io/SubZer0
β‘οΈ @RootAccessClub | 266 |
| 10 | Your X links are snitching on you.
https://x.com/BugCod3/status/2115837807537299777 | 383 |
| 11 | What do you think would be the right response?π€
To submit your answer, visit the link below: https://bugcod3.com/quiz | 364 |
| 12 | π open-sesame
An AI web-pentest skill for Claude Code. Point it at a site you're authorized to test β it maps the attack surface, works through the OWASP WSTG, validates findings, and writesβ¦
git clone https://github.com/hassan-algo/open-sesame
βοΈ 96 Β· 𧬠HTML
π GitHub
#Recon #WebSecurity #ActiveDirectory #Pentest
π€ @RootAccessClub Γ @BugCod3 | 423 |
| 13 | π¨ PHP2Shell β when the bug is in PHP itself
Not a plugin. Not a framework. The interpreter behind most of the web got hit with pre-auth RCE β and AI helped find it (WSJ & NYT covered it).
π§ The two bugs
β’ CVE-2026-109618 β RCE via out-of-memory corruption
β’ CVE-2026-109619 β use-after-free via stale request state (session.upload_progress)
β’ CVSS 9.2 Β· no auth Β· fires before your app code even runs
β’ Highest risk on Apache mod_php β also FPM, php-cgi, FrankenPHP, LiteSpeed
π― The twist nobody mentions
Mass scanning was instant (millions of hits within a day). But a reliable, universal exploit is HARD β memory_limit, same-worker races, and ASLR all get in the way. We break down exactly why.
π‘ What to do
β’ Patch: PHP 8.2.35 / 8.3.36 / 8.4.27 / 8.5.12 β the only real fix
β’ Affected from PHP 5.4.0 onward β on CISA KEV, exploited in the wild
π Full write-up β source-level breakdown + what it means for bug hunters:
bugcod3.com/p/php2shell-preauth-rce-cve-2026-109618-109619 | 379 |
| 14 | π Clavis β JWT Attack Multitool
Stop juggling half a dozen scripts to test one token. Clavis runs the full JWT attack chain from a single binary β zero dependencies, works on Linux, macOS & Windows.
βοΈ What it does
β’ decode & audit β instantly flags weak configs
β’ crack weak HMAC secrets with a wordlist
β’ alg:none signature bypass
β’ RS256 β HS256 algorithm confusion
β’ kid header injection β path traversal / SQLi
β’ jwk & jku header injection β self-signed keys
β’ forge any token on the fly
β’ scan β extract JWTs from HAR files, logs & JS
β‘ Install
go install github.com/MRvirusIR/clavis/cmd/clavis@latest
(or grab a prebuilt binary from Releases)
π Links
GitHub β https://github.com/MRvirusIR/clavis
Write-up β https://bugcod3.com/p/jwt-attack-playbook-weak-secret-to-account-takeover
Free & open source. Built for bug bounty. π
#bugbounty #JWT #appsec #pentest #infosec #BugCod3 | 326 |
| 15 | SubZer0Robot is live β‘
SubZer0 now lives inside Telegram π€
π¨ Early warnings β new exploitation waves, posted the moment they're detected
π΄ Fresh CISA KEV entries β actively exploited CVEs, automatically
π± Mini App β the full CVE tracker, PoCs and dossiers right inside Telegram
π Live layer refreshed every ~15 min Β· Ed25519-signed data
π€ mini app
π Alerts land
π Web
by @BugCod3 & @RootAccessClub | 360 |
| 16 | π¨ One click. Full account takeover.
A forgotten subdomain. A lazy OAuth check. On their own? Two boring "low" bugs.
Chained together? I took over any account with a single link β and got paid 4 figures. β±οΈ 3 hours from recon to PoC.
I broke down the FULL kill-chain β every command, every request, every bypass:
π Finding the dangling DNS record
πͺ£ Claiming the dead subdomain
π Breaking the redirect_uri allowlist
π£ Stealing the OAuth code β session
π Read the full write-up (free, no signup):
π bugcod3.com/blog
The lesson that levels up your hunting: severity lives in the CHAIN, not the bug.
#BugBounty #AccountTakeover #OAuth #Recon #CyberSecurity | 426 |
| 17 | π bugcod3.com is LIVE
From Shadows To Shells β the BugCod3 channel now has a home π΄ββ οΈ
π§° Arsenal β 176+ hacking tools, searchable, with live GitHub stars
π° Feed β every post from this channel, filterable by tag
π§ͺ Lab β reverse shells, JWT debugger, XSS payloads, encoders, hash IDβ¦ 100% in-browser
π§ Daily Quiz β earn points, keep your π₯ streak, climb the leaderboard
βοΈ Write-ups β deep-dive bug bounty articles
π 2FA + GitHub/Google login Β· π² installable on your phone
π² Hit "Surprise me" in the Arsenal
π Psstβ¦ type "hack" on the site
π https://bugcod3.com
Learn β’ Hunt β’ Dominate β‘οΈ
#BugBounty #Tools #CyberSecurity | 474 |
| 18 | π¨ PHP2Shell is live on SubZer0
Two critical PHP core flaws, CVSS 9.2:
CVE-2026-109618 + CVE-2026-109619
One unauthenticated request can lead to remote code execution.
β
Fixed in: PHP 8.5.12 Β· 8.4.27 Β· 8.3.36 Β· 8.2.35
π On the site: 30+ public PoCs (updated every 15 min), scanners, Nuclei templates and official advisories
π https://iliya-bashrc.github.io/SubZer0/
β οΈ Run PoCs only in a test lab
#PHP2Shell #PHP #RCE
@RootAccessClub Γ @BugCod3 | 417 |
| 19 | π Give it a try, share it with your friends π₯
and tell us what you think, we'd love to hear from you! π | 441 |
| 20 | π€« What they'd never say to your faceβ¦ lands here, anonymously.
Create your personal WhisperTopic link, drop it in your bio or story, and let anyone message you without revealing who they are π
β¨ Why WhisperTopic?
π A private topic for every sender, no more messy chats
π― Message anyone anonymously
π Seen receipts, know when your message is read
βοΈ Edits & β€οΈ reactions, everything stays in sync
π‘ Profanity filter & one-tap block
π Identity revealed only with consent
π² Ready-made story prompts
π Your identity is never revealed.
π Get your free link now:
π€ @WhisperTopicBot
https://t.me/WhisperTopicBot
β‘οΈ Powered by @BugCod3 | 449 |
