BugBounty & Hacking Resources – Telegram
BugBounty & Hacking Resources
1.18K subscribers
22 photos
2 videos
5 files
362 links
Download Telegram
تا الان استوری هایی که گذاشته شده خوب بوده یا نه نظر خود را اعلام کنید 👊
Anonymous Poll
82%
عالی ادامه بدید 🦍🤣….
18%
ناموسن ادامه ندید ….☺️
1
“bug bounty as we know it probably dies.”

Couldn’t of said it better myself tbh. Although I think we are 3-5years away from this. People doing bug bounties full time should be planning for the future (I know I am)

https://x.com/zseano/status/1932719746538996157?s=61
😢4🤔3
BugBounty & Hacking Resources
چقدر از این خبر کونتون ترسید ؟🦍
my personal opinion:
این واسه همه زمینه ها برقراره و فقط باگ بانتی نیس
و به نظر من کل cyber security جز اخرین ها هستش که از بین بره

در هرصورت تو این فرصت 10x کار کنید🫦

edit:
و با زیشانو در مورد تایم موافقم😬
Please open Telegram to view this post
VIEW IN TELEGRAM
931
This is how DOM clobbering works.

When you create an element with an id, the browser automatically creates a global variable for that ID:


<a id="foo"></a>


Now
window.foo
points to that single element.

But when you create multiple elements with the same id:


<a id="foo"></a>
<a id="foo"></a>


Now

window.foo
becomes an HTMLCollection, not a single element.

Add a name attribute:


<a id="foo" name="bar" href="..."></a>


And

window.foo.bar
now points to that element (works in Chromium/WebKit browsers, but not Firefox).

Now combine that with a common JS pattern like:


var someObject = window.someObject || {};


This is meant to provide a fallback if the global doesn't exist. However, if
window.someObject
has been clobbered by injected HTML, the fallback silently trusts a DOM object instead of a real JS object.

Now imagine this JS logic:


let imgSrc = someObject.avatar;


If an attacker clobbered
someObject.avatar
with:

<a id=someObject></a>
<a id=someObject name=avatar href='cid:"onerror=alert(1)//'></a>

If HTML is set via innerHTML or similar, then this could render as:

<img src="cid:" onerror="alert(1)//"">
732
Please open Telegram to view this post
VIEW IN TELEGRAM
👍21
How to survive the AI wave in #bugbounty:

- Learn to utilize AI in your hacking flow
- Don't worry too much because automated AI is never going to *fully* replace us. There are lots of programs out there which will be hard for an AI to test fully. 😡🤬

https://x.com/zseano/status/1938144252992884824?s=46
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥6
let's do some mass hunt
51
https://nostarch.com/zero-day
این کتابو هرجور نشده تهیه کنید و بخونید
من نمیتونم اینجا چیزی بذارم یا بگم.
ولی دنبالش باشید
🙏21👍1
Forwarded from Electro0ne Bytes 🦅 (ᴍͥᴏᴇͣɪͫɴ)
Think like a developer, act like an attacker. Study how applications are built before you try to break them. Understanding architecture, common frameworks, authentication flows, and data handling patterns will give you a huge edge. Don’t chase bugs randomly — build hypotheses, validate them, and go deep. And most importantly, document everything. A disciplined hacker is a dangerous one. 😡😎
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥1243
این 8 تا پولامو بدن من دیگه غنی میشم
🔥12
گایز طبق تجربه کوچیکم یه چیزی میگم:
بعضی وقتا یه باگ پیدا میکنین مثلا unpredictable idor
و سریع میرین گزارش میدین اشتباهه

اگر باگ رو به سختی پیدا کردین صبر‌کنین و برین راهی برای predictable کردنش پیدا کنین

من واسه 2 باگ، چند ماه صبر کردم و نتیجه شو گرفتم

الانم دقیقا ۲ تا دارم که برم گزارش بدم مدیوم میشن
ولی گذاشتم یه گوشه هر بار میرم یه سیخی میزنم شاید تونستم impact رو بیشتر کنم

یه تایمی براش تعیین کردم، بعدش نشد سریع گزارش میدم
25