Explore tweets tagged as #log4shell
@nav1n0x
N$
1 day
Guys, whoever is using my Log4Shell/Log4J payload from Pastebin, make sure to replace my token ( with your own. I don’t mind though. 😅
Tweet media one
8
10
179
@intigriti
Intigriti
2 days
💡 Tip!. Injecting Log4Shell payloads is also possible in PDF files! eelyvy has a dedicated GitHub repository showing exactly how to craft your PDF payload file! 😎. 🔗
Tweet media one
2
97
408
@intigriti
Intigriti
4 days
Easiest way to test for Log4Shell (even in 2025) 🤠 . Example 👇
Tweet media one
1
20
166
@intigriti
Intigriti
4 days
Latest Bug Bytes is live! 🚀. This month's issue is as usual packed with bug bounty tips:.✅ Exploiting Log4Shell (Log4J) in 2025.✅ An indispensable GitHub recon tool (not the one you have in mind) .✅ Advanced WAF evasion techniques. & much more! 😎.
Tweet media one
2
9
63
@intigriti
Intigriti
25 days
For some bug bounty hunters, the Log4Shell hunt never truly ended. 😈. While most moved on, some researchers know this vulnerability is still hiding in production systems across the web, even today 👀. We just published a comprehensive guide showing exactly how to uncover
Tweet media one
2
26
167
@InfoSecComm
InfoSec Community
4 months
🚨 New Writeup Alert! 🚨. "Exploiting Log4Shell: How Log4J Applications Were Hacked" by MrXcrypt is now live on IW!. Check it out here: #vulnerability #log4j #log4shell #cve202144228 #exploitation.
0
2
13
@kaspersky
Kaspersky
1 month
🔥 #APTs in 2025 still abuse ProxyShell, Log4Shell, & Fortinet flaws. ⚠️ Patch or become a breach headline. 📖 Full Q1 2025 findings: #ThreatIntel #CyberAttack #StaySecure #APTs #CyberDefense #ZeroTrust #Cybersecurity #Kaspersky #Securelist #Linux
Tweet media one
Tweet media two
1
3
9
@adhirajhangal
Adhiraj Hangal
2 months
🧵 How Open Source Communities Handle Security Crises - and what founders & solo builders can learn. Two of the biggest software vulnerabilities in history:.- Heartbleed (2014).- Log4Shell (2021). Let’s dive in👇
Tweet media one
1
0
2
@Crowd_Security
CrowdSec
2 months
(🧵Thread) CVE-2021-44228 (Log4j Scanning Campaign) Is Back and Stronger than Ever. 4 Years after the exploit was first published, the CrowdSec Network still detects active campaigns targeting the Log4Shell class of exploits. (🧵1/6)
Tweet media one
1
1
4
@mubix
Rob Fuller
24 days
I use Log4shell canaries in my passwords and I have one per website. It’s been crazy interesting the sites that I have gotten pings for and where the pings are from. I think it’s cool. It would be a fun talk to put together and a good story to tell but not useful….
35
58
829
@intigriti
Intigriti
7 days
Breaking down how the Log4Shell attack works 👇
Tweet media one
1
3
6
@impratikdabhi
Pratik Dabhi
26 days
🌐 Server-Side Bugs That Pay Big. • SSRF (internal request abuse).• SSTI (template injection).• XXE (XML Entity Injection).• Log4Shell-style payloads.• Blind bugs with Burp Collaborator. 💣 Quiet bugs, massive impact. #BugBounty #SSRF #EthicalHacking #bugbountytip.
1
11
96
@_Nidouille_
𝓝𝓲𝓭𝓸𝓾𝓲𝓵𝓵𝓮 🐙🐙
27 days
Putain, 8 failles de sécu qui ont de belles répercussions. l'IT est un château de carte que l'on redécouvre a chaque faille de sécu importante, coucou OpenSSL, Log4Shell, etc.
1
16
21
@DebugPrivilege
DebugPrivilege
1 year
When you see java.exe spawning weird child processes, it’s time to investigate. I will be doing a write-up of analyzing a Log4Shell payload via a memory dump!
Tweet media one
@0xdf_
0xdf
1 year
Crafty from @hackthebox_eu is about exploiting a Minecraft server. I'll use an open source client to send a Log4Shell payload, and get a shell. Then I'll find admin creds in a custom plugin. In Beyond Root, I'll explore the web.config file.
0
14
96
@1336_0ff_by_0ne
1336_0ff_by_0ne
7 months
I'm trying something different. 3 inch Velcro patches for Crowdstruck, Solorigate, MOVEit Transfer and Log4shell. In recognition of analysts and responders who handled these major incidents, working nights, weekends and holidays. I think of them as merit badges.
Tweet media one
3
7
56
@jfrog
JFrog
7 months
Our JFrog Senior Solution Engineers break down how to protect your applications this December and beyond. Learn key steps to safeguard your code and keep the on-call pager silent: #Log4J #CyberSecurity #Log4Shell #DevSecOps
0
0
0
@lcamtuf
lcamtuf
8 months
Vuln names: this is log4shell. We named it this way because it's in log4j and gives you shell. Threat actor names: this is HAIRY EEL, aka VIOLIN HIPPO, no relation to VEXING MACKEREL. Also known as APT-74, formely APT-C-92. We named it this way because he's a guy in Bulgaria.
5
80
421
@yeswehack
YesWeHack ⠵
9 months
📝 #OpenSource #BugBounty Spotlight: @ApacheLog4j – A Java-based logging utility, this @TheASF project monitors runtime behaviours and flags errors. Also the location of Log4Shell, possibly the worst-ever vulnerability. Five scopes and €10k max rewards via @sovtechfund 🚀 1/4
Tweet media one
1
3
8
@jfrog
JFrog
7 months
Three years later, #Log4Shell is still a wake-up call. Thankfully JFrog experts, Richard Clark and Gabe Martino, demonstrate how you can create a Curation policy by leveraging the JFrog integration with @github's CoPilot. Get a refresher on the risks and actions you can take
0
0
1