AI just killed half the software industry.
Microsoft Office
Microsoft Excel
Microsoft Word
Microsoft PowerPoint
Microsoft Access
Microsoft Visio
Microsoft OneNote
Microsoft Project
Microsoft Power BI
Microsoft Whiteboard
Google Docs
Google Sheets
Google Slides
Google Forms
Google Looker
Google Workspace
Adobe Acrobat
Adobe Photoshop
Adobe Illustrator
Adobe InDesign
Adobe Express
Adobe Creative Cloud
Adobe XD
Canva
Canva Whiteboards
Figma
FigJam
Sketch
Miro
Mural
Excalidraw
TLDraw
Draw.io
Lucidchart
Lucidspark
Whimsical
Gliffy
Creately
Eraser
Napkin
Airtable
Notion
Notion Databases
Coda
Obsidian
Obsidian Canvas
Smartsheet
Monday.com
Asana
ClickUp
Trello
Zoho Sheet
Apple Numbers
Apple Pages
Apple Keynote
Apple Freeform
LibreOffice
LibreOffice Calc
LibreOffice Impress
Tableau
Looker
Qlik
Domo
Metabase
Hex
Julius
Mode
Sigma
ThoughtSpot
Omni
Lightdash
Preset
Redash
Deepnote
Observable
Evidence
Datawrapper
Flourish
Polymer
Akkio
Rows
Equals
Causal
Pigment
Quadratic
Sourcetable
Grist
Baserow
NocoDB
SeaTable
Stackby
Milanote
Stormboard
Conceptboard
Klaxoon
Heptabase
Kinopio
Zoom Whiteboard
Pitch
Beautiful.ai
Gamma
Prezi
Mentimeter
Slido
Decades of software development. Billions in market value.
And then someone typed a prompt.
Everything's totally fine. Nothing to see here. 🙃
1
262
I'll never understand these people. They have the world at their feet—wealth, power, influence, everything they could ever want. And yet, somehow, they manage to lose it all over a pair of boobs. #Trending #CurrentEvents #WorldNews #Scandal
1
197
These days on Bugcrowd, if your finding isn't an RCE, you're lucky if you even get a response after two months of waiting. #bugbounty
1
295
Bug bounty hunters: Is GraphQL introspection enabled still worth reporting in 2026, or is it almost guaranteed to be closed as Informative?
#bugbounty #bugbountytips
8
17
2,408
#binance stop hiring idiots and trusting them with our money on their laptops.
3
280
The Industries rarely recognize their turning points while they're happening. The real consequences only become clear years later.
Bug bounty is changing at its core, and nobody truly knows what will emerge on the other side.
#BugBounty #CyberSecurity #InfoSec
4
604
How hackers stole $2.6 MILLION from #Polymarket without stealing private keys.
On October 29, 2026, attackers exploited a third-party JavaScript supply chain compromise to drain approximately 28.6 million POL tokens from Polymarket users.
Here's how the attack worked 👇
1️⃣ Supply Chain Compromise
Polymarket was loading a legitimate performance monitoring script from DebugBear:
cdn.debugbear.com/C7xcKKrjUn…
Attackers managed to replace the original 60,493-byte JavaScript file with a malicious 15,187-byte payload.
The exact mechanism used to compromise the script delivery remains unclear.
2️⃣ Harvesting Browser Data
Once loaded on polymarket.com, the malicious JavaScript executed with the site's origin privileges.
It accessed sensitive data stored in the browser's localStorage:
• polymarket.auth.params
• polymarket.auth.proxyWallet
• poly_clob_api_key_map
These contained authentication, wallet-related and trading API information.
3️⃣ Hijacking Polymarket's Trading Infrastructure
Instead of simply stealing credentials, the malware traversed Polymarket's React component tree to locate its internal trading client, exposing:
• createOrder()
• postOrder()
The attackers then abused Polymarket's legitimate trading infrastructure to execute fraudulent transactions.
4️⃣ Draining User Funds
The payload used different methods depending on the victim's authentication type:
🔹 Self-custody wallet users:
Outcome tokens were transferred using safeBatchTransferFrom() to an attacker-controlled address.
🔹 Email-authenticated users:
Positions were liquidated through fill-and-kill sell orders, progressively lowering prices from 97% to 50%, then to the minimum tick.
🔹 Available cash balances:
Funds were routed through Polymarket's Collateral Offramp, converted into POL via fun.xyz and Relay, and delivered to the attacker's wallet.
Transactions passed through Polymarket's legitimate relayers and Deposit Wallet Factory, making the malicious activity resemble normal platform operations.
5️⃣ Why Content Security Policy (CSP) Failed
Polymarket had CSP enabled, but its policy explicitly trusted the compromised infrastructure:
• cdn.debugbear.com — allowed JavaScript execution
• data.debugbear.com — allowed network connections
• *.polymarket.com — trusted API traffic
• *.fun.xyz — allowed transaction-related requests
The script URL never changed. Only its contents did.
Consequently, CSP host allowlisting did not block the malicious payload.
6️⃣ The Impact
Blockchain analysis identified:
• Approximately $2.6M stolen
• 28,636,284 POL accumulated
• 36 batch transfers of outcome tokens
• 33 affected deposit wallets in those transfers
• 31 different relayer addresses
The attack operated for roughly 50 minutes before Polymarket removed the DebugBear integration.
7️⃣ How Could This Have Been Prevented?
✅ Subresource Integrity (SRI) to verify JavaScript hashes before execution.
✅ Integrity Policy to enforce integrity checks on external scripts.
✅ JavaScript integrity monitoring to detect unexpected changes in third-party code.
✅ Strict controls over sensitive browser storage and privileged trading operations.
#Polymarket #CryptoHack #Cybersecurity #Web3 #SupplyChainAttack #JavaScript #BugBounty #DeFi #InfoSec
A prompt that can save you hours in front of the computer : ♦"Do not interrupt me with approval requests, confirmation prompts, or unnecessary questions. Use your best judgment to make decisions independently, execute all necessary tests, and continue autonomously until the assessment is fully completed. Do not stop after intermediate results or ask for permission at every step. Stay within the authorized scope, handle obstacles proactively, and deliver a comprehensive final report with validated findings and supporting evidence." ♦ #bugbounty #bugbountytips #ia
12
500
If I were the guy behind the alleged Binance hack, I'd launch the biggest airdrop in history and give away $3 BILLION to random crypto users. 💸
The cops would be hunting me down, but I'd have the people on my side. 😂
#RobinHood #Binance #Crypto #Airdrop #CryptoHack
5
361
Question : How did attackers allegedly obtain valid EIP-7702 authorization signatures?
My theory: phishing or social engineering, followed by compromised employee or signing access. We've seen similar patterns before...
#Binance #CryptoHack #EIP7702
119
🚨 How was Binance reportedly hacked?
Attackers allegedly exploited Ethereum's EIP-7702 to delegate a hot wallet's execution to malicious smart contract code.
Just 3m24s later, a sweep() call reportedly drained 167,464 ETH and 63 tokens without requiring another signature.
How the initial authorization was obtained remains unknown.
#bugbounty #Ethereum #binance #hacking
2
203
Polymarket users' funds stolen. Binance reportedly hacked, with over $3 BILLION allegedly funneled from hot wallets through Tornado Cash. A new Sendmail zero-day reportedly being exploited to send emails on an industrial scale…
And people say the cybersecurity industry is having a rough year. 😂
At this rate, 2026 deserves its own Netflix series. 🍿🔥
#Cybersecurity #Binance #HappyNewYear #Trump #USA #BugBounty
154
Hey
@grok
, how long until AI can fully replace me at my job?
I'm a Bug bounty hunter.
Be honest.
4
20
6,513
The same thing is happening to the Bug Bounty Hunter. 🚨
#BugBounty #bugbountytips #CyberSecurity #InfoSec #EthicalHacking #pentest #Hacker
5
464










