Top Tweets for #log4shell
i get nervous everytime i read there was some pwn on minecraft.
ptsd-dog.jpg
#log4shell
This is a really impressive exploit.
https://t.co/HCkKuroNLn
Hey bug bounty hunters 👋Apache log4j is not dead. Before you skip Apache log4j targets in 2026 — read this : https://t.co/tJ5lHaoFcv
We documented exactly where, how, and how to report it clean.Drop everything and read:
#BugBounty #Log4Shell #BugBountyTips

@ADanielHill @ObservadorUY imagine the laughs if it was SO Wide Open this worked? .. it HAS happened before. 😂 ¿Imaginen las risas si fuera TAN abierto que esto funcionara? ... Ya ha sucedido antes. 😂 #ShutDown #Cerrar #Log4Shell

Viele Java-Teams wissen nicht, welche Libraries wirklich produktiv laufen — bis die nächste #Log4Shell auftaucht. #SBOMs schaffen Transparenz über Abhängigkeiten & Risiken.
Sven Ruppert zeigt die Praxis:
https://t.co/nYkBtoQKzq
https://t.co/DmCGOjg1dg
#Maven #Gradle #CycloneDX

#RCE attempt targeting Apache #log4j #log4shell #RondoDox
2026-05-03 02:23:34 UTC
Source IP: 124.198.131.185 🇺🇸
GET /
IOCs:
45.92.1.50 🇳🇱
hxxp://45.92.1.50/rondo.dus.sh
rondo2012@atomicmail[.]io
![sicehice's tweet photo. #RCE attempt targeting Apache #log4j #log4shell #RondoDox
2026-05-03 02:23:34 UTC
Source IP: 124.198.131.185 🇺🇸
GET /
IOCs:
45.92.1.50 🇳🇱
hxxp://45.92.1.50/rondo.dus.sh
rondo2012@atomicmail[.]io https://t.co/atmJdcdnwY](https://pbs.twimg.com/media/HHewndZWMAAJB9o.jpg)
Log4Shell is the attack that made us aware of the security risks if we are not careful in network programming in Java. With this book, you will know what to watch out for.
#javaprogramming
#Security
#vulnerability
#Programmer
#Log4Shell
#AWS
https://t.co/ChB78xYOsj
7mhGvMlr
You trust your dependencies? That’s the risk. From #Log4Shell to self-replicating worms, attacks don’t hit your code first — they hit your supply chain, often via packages.
@MohammadAliEN explains what to watch: https://t.co/RnVHRmxgIE
#AppSec #Java #SupplyChainSecurity

If your #Java stack relies on “upstream will fix it”, you already lost time. @spoole167 shows how real-world Java systems survive on unmaintained code — and what to do instead.
Learn from the #SupplyChain reality: https://t.co/DFnNNDep6s
#CyberSecurity #AI #Log4Shell

Log4Shell wasn’t just a vulnerability. it was an exposure of how deeply logging is embedded in modern apps.
Read Full Blog Here : https://t.co/F1emMFPAhW
#Log4Shell #CyberSecurity #AppSec
First time with Log4Shell — Unified (HTB Tier 2) delivered.
JNDI payload → Burp intercept → rogue LDAP → shell → MongoDB → root 🎯
CVE-2021-44228 isn't just a headline anymore.
Full breakdown 👇 https://t.co/yXsV6ckoPT
#HackTheBox #Log4Shell #CTF
Is your [build.gradle] file lying to you? 🛑
You might only declare 10 dependencies, but Gradle is resolving hundreds. In those hidden transitive layers, vulnerabilities like #Log4Shell or the recent #npm exploits find a home.
If your #Gradle projects live on #GitHub, you’re already halfway to a solution! 🎉
By integrating Gradle with GitHub’s Dependency Graph via the official Dependency Submission Action, you get:
✅ Full Transparency: No more guessing what’s in your graph.
✅ Automated Alerts: #Dependabot identifies CVEs in real-time.
✅ Rapid Response: Use Build Scan® to trace exactly why a vulnerable version was selected (constraints, substitutions, or transitive paths).
For enterprise-scale security, Develocity takes this further, allowing platform teams to audit every build across the entire org—including local developer machines.
Stop guessing. Start observing. 🛡️
🔗 https://t.co/iHM1Mia4MA
#Dependabot #AppSec #DevSecOps #SoftwareSupplyChain #Develocity

#Log4Shell didn’t break #Java — it revealed it. @spoole167 shows how decades of “it still works” thinking left the Java #SupplyChain exposed & why maintenance is now a legal obligation.
See what regulators expect from Java teams: https://t.co/DFnNNDep6s
#CyberSecurity #AI

🔍 CVE-2021-44228 (Log4Shell)
Three years later, Log4Shell is still being scanned for on the internet every single day.
Why?
Legacy Java apps
Forgotten containers
Vendors who never backported fixes
👉 Breakdown & mitigation:
https://t.co/uENaB8ziJ6
#CVE #Log4Shell #CyberSecurity
Threat hunting in 2026 shifts to proactive defense by analyzing attacker behaviors and patterns. AI automation handles routine risks, enabling strategic human decisions for long-term security. #ThreatHunting #AIinSecurity #Log4Shell
https://t.co/Ol7FQprpQ3
Who is responsible for your #Java dependencies when upstream disappears? @spoole167 traces how #Log4Shell exposed the reality of #OpenSource maintenance and why SBOMs, CRA & NIS2 changed the rules.
Learn what “responsibility” means now: https://t.co/DFnNNDep6s
#SupplyChain

ネットワークプログラミングをJavaでやるとき、気をつけないとセキュリティリスクを負う、というのを知らしめたLog4Shell。この本で現象が確認ができる!
#Java
#セキュリティ
#脆弱性
#セキュアプログラミング
#プログラマ
#Log4Shell
#AWS
https://t.co/BO9mpJsI4p
zVioKD2G
Last Seen Hashtags on Sotwe
Most Popular Users

Elon Musk 
@elonmusk
240.2M followers

Barack Obama 
@barackobama
119.3M followers

Donald J. Trump 
@realdonaldtrump
111.6M followers

Cristiano Ronaldo 
@cristiano
108.8M followers

Narendra Modi 
@narendramodi
106.9M followers

Rihanna 
@rihanna
97.2M followers

NASA 
@nasa
92.1M followers

Justin Bieber 
@justinbieber
90.5M followers

KATY PERRY 
@katyperry
86.7M followers

Taylor Swift 
@taylorswift13
80.5M followers

Lady Gaga 
@ladygaga
72.1M followers

Kim Kardashian 
@kimkardashian
69.3M followers

YouTube 
@youtube
68.6M followers

Virat Kohli 
@imvkohli
68.4M followers

Bill Gates 
@billgates
63.4M followers

The Ellen Show
@theellenshow
62.5M followers

CNN 
@cnn
61.9M followers

Neymar Jr 
@neymarjr
61M followers

X 
@x
60.9M followers

CNN Breaking News 
@cnnbrk
59.9M followers






![sicehice's tweet photo. #RCE attempt targeting Apache #log4j #log4shell #RondoDox
2026-05-03 02:23:34 UTC
Source IP: 124.198.131.185 🇺🇸
GET /
IOCs:
45.92.1.50 🇳🇱
hxxp://45.92.1.50/rondo.dus.sh
rondo2012@atomicmail[.]io https://t.co/atmJdcdnwY](https://pbs.twimg.com/media/HHewjSQXMAACM4A.png)
![sicehice's tweet photo. #RCE attempt targeting Apache #log4j #log4shell #RondoDox
2026-05-03 02:23:34 UTC
Source IP: 124.198.131.185 🇺🇸
GET /
IOCs:
45.92.1.50 🇳🇱
hxxp://45.92.1.50/rondo.dus.sh
rondo2012@atomicmail[.]io https://t.co/atmJdcdnwY](https://pbs.twimg.com/media/HHewNtsXUAI2ZBP.png)








