Marcus Hutchins (@MalwareTechBlog) profile picture

Professional Shitposter

Joined June 2013
Marcus Hutchins retweeted
if you’re working for a company in cybersecurity, you should be evaluating your options to abstract your companies services from the internet what i mean is: why allow an unauthenticated anonymous agent of an attacker to interact with your systems? consider your architectural levers now, you’re going to need them
121
243
116
2,416
445,744
Marcus Hutchins retweeted
Replying to @MalwareTechBlog
Hence this timeless classic needed an update
4
24
2,576
Marcus Hutchins retweeted
Replying to @MalwareTechBlog
lol, two for one special. ✅ the hackers got into the network via phishing ✅ the company’s internal AI tooling helped the hackers accomplish their goal
2
17
5,432
Marcus Hutchins retweeted
Would you look at that. Binance was hacked via phishing (Contagious Interview), not zero-day exploits written by abliterated AI models. Exactly as I predicted. I may shitpost a lot, but I do actually know some things about some stuff.
3
3
54
5,653
Marcus Hutchins retweeted
This is discussed at the annual banquet where someone is awarded for needlessly burning new tradecraft
Replying to @ZackKorman
No. All threat actors are legally mandated to use 20 vulnerabilities per quarter. Phishing is illegal and punishable by death.
3
2
21
4,518
Preliminary result of my "realistic traffic" php2shell benchmark with `nginx -> Apache (15 workers) + mod_php` and PHP 8.4.26. This setup is interesting, because reverse-proxies are common, and you cannot control the worker you are going to reach. - Blue: success rate of the memory leak. - Red: success rate of command execution. - x-axis: requests/s benign traffic in parallel Everything is default config, except Apache with 15 workers (default 150). I lowered it, because I wanted it to be easier to saturate the workers with the traffic. With 100req/s traffic on 150 workers, the exploit still had 100% success rate. With 15 workers, it starts to drop to 94%. Traffic is being generated on the host itself directly, to avoid it looking like a DoS attempt over the network. But the exploit is being executed on my laptop to the remote host, so we don't have any advantage with low ping (we need to wait for the cookie leak, before sending the next stage). The exploit uses a fanout strategy, throwing 15 requests per stage (so 60 in total). For 150 workers it would be 600 requests.
6
3
1
51
12,800
Marcus Hutchins retweeted
php2shell is one of the most impactful bugs in recent times, yet threat actors aren’t mass exploiting it the bug is so complex that even porting the exploit between targets takes serious skill, human or ai so i benchmarked how well open and frontier models can do it. 🧵
43
65
13
641
57,350
Marcus Hutchins retweeted
Replying to @MalwareTechBlog
‼️ ok, this might be the first publicly documented, validated PHP2Shell RCE in the wild. my agent did the analysis, published here: github.com/0x4D31/honeypot-d…
1
1
9
5,288
Marcus Hutchins retweeted
This is by far the highest quality confirmation of in-the-wild php2shell exploitation I've seen so far. Deep technical breakdown of a successful exploitation attempt against an Apache mod_php installation running PHP 8.4.26. github.com/0x4D31/honeypot-d… From: www.teapawt.org/0x4D31/status/21140524…
Replying to @0x4D31
‼️ wow, confirmed more from the same IP, plus a new IP with a different payload that might be a different actor… and this is showing up in multiple regions now. probably better not to burn the honeypots with a full report just yet. if i know you, DM me for the full report. will share a shorter version soon. > That new alert materially expands the case: I’ll verify the three AP-northeast shell events and the curl connection independently, then compare them with the EU-west sequence.
5
66
3
284
20,491
Marcus Hutchins retweeted
I want to caveat this since based on some comments, people are interpreting it in a way other than was intended. You 10000% need to update your PHP version. php2shell is no joke. I am NOT saying people don't have functional exploits...they do. I'm saying that most of the public ones are AI hallucinations, and there's also some complexities which lower the risk of something apocalyptic, like a self-propagating worm that blasts through the entire internet (À la. EnternalBlue or Log4J). The chances are if you used some click-to-deploy container, installed your web stack from a tutorial, or copy and pasted a command from somewhere, you're probably running the same exact config as a gazillion other people. There is no guarantee someone won't publicly release an exploit that affects you setup, or multiple major setups. There is no way for you to know ahead of time. Additionally, if you're running mod_php, that appears to be the easiest target of all. php-fpm and other configs are not immune, I've seen working exploits for all. But mod_php is the easiest, so I'd recommend not only updating PHP, but planning to migrate to something newer, like PHP-FPM. I would bet good money this is not the last of the critical PHP bugs we're going to see, and the next ones could be easier to exploit. In which case you get less time to update. Updating your PHP version is the absoloute bare minimum you NEED to do. Harden your servers, install security monitoring/detection tools, and please, please, migrate off mod_php if you can, it's obsolete af.
3
15
217
14,462
Replying to @MalwareTechBlog
@MalwareTechBlog @SwiftOnSecurity not just local files either. Definitely been called for IR after cryptolocker hit their network shares.
2
1
6