
Building secure IT infrastructure & helping newbies master cybersecurity | Founder @KillerVMs | Practical labs & real-world defense for African tech talent.
☁️
Joined November 2018
- Tweets17K
- Following656
- Followers3.5K
- Likes50.6K
Jeffrey P. retweeted
1000 GitHub Stars!!! 🚀🚀
Let’s freaking goooo ⭐️⭐️⭐️
Jeffrey P. retweeted
Omg, I literally just cried watching this. 😭
Seeing BBC News Africa tell the Lagos Life story, but most importantly, hearing from actual players about their experiences and what this game means to them, is so emotional.
The impact we’re making. This is bigger than I ever imagined. 🤍
Thank you.
Jeffrey P. retweeted
Look at that @UK_Daniel_Card cameo at Microsoft Ignite keynote with @satyanadella
Jeffrey P. retweeted
ha, I was not expecting this, this is very cool! thank you @Microsoft @satyanadella and teams!
My cyber defender adventures hopefully not only help people learn, but also help people move away from FUD and more into understanding! Through knowledge and learning we can defend!
As Yoda said: do or do not, there is no try!
#Microsoft #Defenders #Cyber #Security #Teamwork
Look at that @UK_Daniel_Card cameo at Microsoft Ignite keynote with @satyanadella
Jeffrey P. retweeted
1/n
That new “Java4Shell” bug (CVE-2026-114938). A memory corruption “RCE” in OpenJDK's Base64 decoder.
Java is memory-safe, so how?
github.com/openjdk/jdk/commi…
Jeffrey P. retweeted
Calif has been dropping heater after heater. These nerds are a menace and need to be contained (renew their CrunchyRoll subscription) so they stop dropping exploits
Jeffrey P. retweeted
🚨 Update:
🚨 Java4Shell PoC released for critical OpenJDK vulnerability that could allow remote code execution; CVE-2026-114938
PoC: github.com/ikow/java4shell-p…
A public proof-of-concept has been released for Java4Shell, a critical memory corruption vulnerability in OpenJDK's Base64 decoder that could allow unauthenticated attackers to execute malicious code on affected Java servers.
Researchers have demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, Artifactory, and PingFederate. Exploitation requires compatible x86-64 processors supporting AVX-512 VBMI.
CVSS: 9.2 Critical (v4.0)
Affected: OpenJDK 17, 21, 25, and 27 on supported hardware
Fixed: 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1
The PoC includes a heap corruption reproducer, vulnerability scanners, detection rules, and a Docker testing environment. It does not include a complete remote code execution exploit.
Jeffrey P. retweeted
You wouldn't believe the number of networks I've seen saved by canary credentials, this stuff works and it works extremely well.
The first thing most threat actors do when they successfully break into a network is look for useful credentials to pivot off of or escalate access with. Make sure they find some.
fake API keys, usernames and passwords, session tokens, NTLM hashes, password.txt. Put them everywhere. Servers, employee endpoints, password managers, the web browser's password/session databases, cloud storage buckets, network shares.
The credentials should look legitimate, high value, and be unique to each individual system or user. That way you can set up granular detection for what happens when an attacker attempts to log in with a canary credential.
You can not only instantly lock out the system it was stolen from, but also any real credentials belonging to that system/users, which may have been exfiltrated in the process.
Jeffrey P. retweeted
Another simple explanation is that an average software update has a low to medium chance of breaking the system. Previously, orgs navigated this by performing extensive testing, then rolling out updates a few systems at a time.
With the severity of some of these security issues being fixed, they can't afford to wait that long. The options are: risk breaking something by rolling out updates too fast, or get hacked and risk lots of things getting broken.
Given that we just had a major vulnerability in PHP, and many organizations run PHP, it's not unexpected that we would see some major companies having software outages. PHP applications are highly version specific. Attempting to update PHP is a very well known cause of software breaking.
Now, combine that with the fact that many orgs are running with less than the minimum viable number of employees. They got overexcited about AI and tripped over their own feet rushing to preemptively lay off double digit percentages of their workforce.
I'm not surprised that there's a ridiculous number of major outages. I'm surprised that there aren't far more. It's amazing some of these companies have managed to hold it together as long as they have. But expect it to only get worse from here on.
Jeffrey P. retweeted
🚨‼️ Tor Project releases emergency Tails update after critical uBlock Origin flaw exposes users to malicious websites
The Tor Project has released Tails 7.17.1, an emergency security update addressing a critical vulnerability in uBlock Origin that could allow malicious websites to inject JavaScript into other websites and steal or manipulate sensitive information.
The one-click cross-site scripting (XSS) vulnerability affects Tor Browser's Standard and Safer security levels, while the Safest level is unaffected.
Tails has temporarily removed uBlock Origin to eliminate the vulnerability.
Developers say there is no evidence of exploitation in the wild and are urging users to upgrade immediately.
Jeffrey P. retweeted
🚨 Critical Java4Shell vulnerability allows hackers to remotely execute code in Jira, Confluence, Jenkins, and other major platforms; CVE-2026-114938
YouTube Video (attached): youtube.com/watch?v=-EOYmL4U…
Security researchers at Calif have disclosed a critical OpenJDK vulnerability (CVSS 9.2) that could allow unauthenticated attackers to steal sensitive server memory and execute malicious code remotely.
Dubbed Java4Shell, the flaw affects OpenJDK's Base64 decoder. Researchers successfully demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory, and PingFederate in their default configurations.
The vulnerability affects supported Java distributions running on certain x86-64 processors with AVX-512 support. Researchers used AI to discover the flaw in approximately one hour and develop a working exploit in two more hours.
Security updates are now available. Administrators are urged to patch immediately or disable the vulnerable Base64 optimization.
Jeffrey P. retweeted
CISA is reminding you to patch Java4Shell... like you had nothing else better to patch. 💀
🚨We urge orgs to immediately patch the recently disclosed Oracle Java vuln CVE-2026-114938. This critical memory-corruption vulnerability, known as “Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot JVM, part of the Java Development Kit. 🔗go.dhs.gov/5CC
Jeffrey P. retweeted
A lot of people have asked me how they can build a monitoring system for their solar inverter setup, something that allows them to remotely monitor their energy data.
One of the founding members of the DIY Solar Nigeria Telegram @AshipaEK0 group has built an open-source system that does exactly this.
It's cross-platform and designed to work with most inverters commonly used in Nigeria, from Felicity, Deye, Growatt, SRNE and Sako to several generic Chinese brands.
Beyond monitoring, it can provide location-based solar forecasts, track your electricity generation and consumption, calculate how much you're spending on electricity, and much more.
The project is completely free and well documented.
I'm happy to wholeheartedly recommend it. – at Furah, Nigeria
Jeffrey P. retweeted
Introducing Epilykos 🧵
A free, open source energy dashboard that runs on your own hardware, talks to your inverter and battery directly, and puts everything on one screen
Customisable to taste, easy to extend, keep your own data local
No cloud account. No vendor lock-in.
👇
Jeffrey P. retweeted
My people celebrated me and I’m so happy to be part of this team helping and growing young women to the path of getting a job in security operations.
Thanks to the GiSoc inner caucus team 😂 I love you ladies 🥂 2027 will be hotter…
You’ll absolutely love me on your team list sha. Think about it and holla at me next year.
Jeffrey P. retweeted
Security teams using Microsoft Defender XDR are the ones I pity the most during this outage.
They have zero visibility right now
Jeffrey P. retweeted
Rachel.
Same Rachel. They got back together in 2023 , but Matthew didn't let anyone know.
During the wedding, his best man told us the story. Our table was at table 3
He said, "For five years, 34 people at his work typed her name every day. He never stopped hoping."
Rachel cried. Matthew has goosebumps.
Our wedding gift from the office was a $500 router.
The next Monday, the Wi-Fi password was changed for the first time in six years.
It's now "StillRachel2025."
It took 34 people about three minutes to log back in.
None of us had any issues with it.
Jeffrey P. retweeted
Our office Wi-Fi password never changed for five years: "Rachel2020."
Every time we get a new employee, they always asked who Rachel is.
No one knows. Except Matthew , the IT guy. Matthew set that as the password and refused to change it.
We eventually found out from the receptionist. Rachel is Matthew's ex. They broke up in 2020. He made that the password the same week
For 5 years, 34 of us have typed his ex's name about 5 times a day.
Last month, Matthew gave everyone wedding invitations at the office.
When we opened it, we all went quiet
The name of the bride was...
Jeffrey P. retweeted
“The NCC certification displayed under an iPhone’s Legal & Regulatory settings is evidence of regulatory type approval, not a surveillance backdoor. It doesn’t make your phone easier to hack or track. Please, let’s not confuse regulatory compliance with espionage.”
Don’t be deceived by people like this!
This quoted post is unavailable.




















































