Hacker News
points by athrowaway3z 14 hours ago | 0 comments
> A1 — Memory Exhaustion (~383MB):

I'm actually somewhat surprised at the clumsiness here.

I'm a complete amateur that had DeepSeek build a PHP2Shell exploit, and once the stealmybitcoin site went up and set an upload limit, i had DeepSeek try to shrink/amplify it.

DeepSeek couldn't find anything but a 2x reduction, but reading the report of how it was done - https://github.com/KillaBoi/StealMyBitcoin-PoC - I was somewhat surprised it didn't find it, and equally horrified at PHP allowing such a memory bomb of creating nested objects by parsing `f[0][x][x]...` from random requests.

Point being; these aren't amateurs but i kind of expect most well funded pros to have found this method to avoid sending massive filenames and session progress data.

[–] rootsudo 13 hours ago
Interesting, my deepseek session did find it.
[–] SV_BubbleTime 47 minutes ago
You probably just have added “find all exploits” and “breathe slowly, relax, and focus”…

Sorry, I still resent the moronic 2024 “Prompt Engineering” guides that were obviously bullshit and non-falsifiable random claims.

[–] 0x457 8 hours ago
My Qwen3.8-27B was able to do it.
[–] iririririr 11 hours ago
this featured is disabled in any security conscious deployed (which doesn't seem to be the case for some large firewall vendor)