From my experience all software developers are now security engineers wether they know it, admit to it or do it. Your code is now the security of the org you work for. #GoldenAgeOfDefense – at Wat Ket, Thailand
Jim Manico from Manicode Security retweeted
🚨 BREAKING: Node.js just dropped its OWN security bombshell.
4 HIGH-SEVERITY vulnerabilities patched TODAY, including one that could let hackers remotely execute malicious code on vulnerable servers.
→ 10 SECURITY FLAWS were addressed in today's Node.js release, FOUR rated HIGH severity.
→ REMOTE CODE EXECUTION: CVE-2026-111497 is a serious flaw in Node.js's Brotli decoder that could allow attackers to execute malicious code remotely.
→ TLS SECURITY BYPASS: Two separate vulnerabilities could trick affected applications into accepting certificates for the WRONG server under certain conditions.
→ Think about that. Your application could establish an encrypted connection while failing to properly verify WHO it's talking to.
→ THREE MAJOR NODE.JS VERSIONS AFFECTED: Node.js 22, 24 and 26 all required emergency security updates.
→ RUNNING NODE.JS 18 OR 20? Those versions are END-OF-LIFE and aren't receiving these official security patches.
→ PATCH IMMEDIATELY: Update to Node.js 22.23.4, 24.22.1 or 26.12.1, depending on your release line. If you're using Docker, rebuild and redeploy your containers.
PHP AND Node.js both facing major security disclosures on the SAME DAY.
If you run a website or application, TODAY is the day to check your servers.
And remember: the public release of security patches can give attackers a roadmap to systems that haven't updated.
Don't be the last one to patch.
🚨 A MASSIVE internet security emergency is unfolding right now. 🚨
Two CRITICAL vulnerabilities have been discovered in PHP, potentially putting millions of websites at risk.
→ NEARLY 70% of websites with a known server-side language run PHP. The potential scale is ENORMOUS.
→ TWO CRITICAL security flaws have been confirmed, each scoring 9.2/10 in severity.
→ Attackers could potentially take control of vulnerable servers remotely, without authentication.
→ Reports suggest PHP versions dating back to 2004 could be affected. The exact scope is still unconfirmed.
→ EMERGENCY PATCHES are scheduled for TOMORROW at 10 AM ET. Website owners are being urged to prepare immediately.
→ Europe's CERT-EU is warning organizations to patch ASAP or consider TAKING EXPOSED APPLICATIONS OFFLINE if they cannot be secured.
→ WordPress, Magento, Laravel and potentially millions of other PHP-powered websites could be at risk.
→ Once patches go public, hackers could reverse-engineer them and race to attack servers that haven't updated.
The vulnerabilities are CONFIRMED. The full technical details remain secret.
Tomorrow, the race between hackers and defenders begins.
This could get ugly. FAST.
The last 48 hours of cyber news is 🔥:
• PHP: critical RCEs
• LiteLLM: compromised release
• eMudhra: CA private keys compromised
• GitLab: CVSS 10 RCE
• FortiSIEM: public RCE exploit
• Signal: call hangup flaw
• Oracle: 1,295 security patches
Respect to the teams responding.
Jim Manico from Manicode Security retweeted
It's days like today with #PHP2Shell responses that remind me to dust off the old "A Few Good Men" spoof I made for why WAFs are critical for a layered defense.
A FEW GOOD WAFS 😂
Jim Manico from Manicode Security retweeted
Invented a new form of WAF???
Uh, your only about 15 years late to the party for correlating inbound/outbound data for detections...
From my @BlackHatEvents talk from 2011
media.blackhat.com/bh-dc-11/…
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
AI writes more code than ever, but security isn't keeping pace.
Our 2026 GenAI Code Security Report found an average security pass rate of just 56%.
Tomorrow, join @WeldPond and @manicode to explore the findings and practical ways to close the gap. veracode.com/resources/webin…
Jim Manico from Manicode Security retweeted
I'm excited to speak with @manicode tomorrow on how LLMs often write code with vulnerabilities if you don't give them any security intent and how we can improve GenAI secure coding.
AI writes more code than ever, but security isn't keeping pace.
Our 2026 GenAI Code Security Report found an average security pass rate of just 56%.
Tomorrow, join @WeldPond and @manicode to explore the findings and practical ways to close the gap. veracode.com/resources/webin…
Jim Manico from Manicode Security retweeted
News: LiteLLM 1.107.0 on PyPI shipped a credential stealer. All 7 wheel files carried malware that runs every time Python starts, even if your code never imports litellm. It grabs SSH keys, AWS, GCP and Azure keys, browser passwords, env vars and CI secrets. PyPI has quarantined the release.
If you installed 1.107.0, treat the machine as hacked. Delete the cook.pth, cook.py and sitecustomize.py files it dropped in site-packages, rotate every key it could reach, and pin an older version.
aisle.com/blog/litellm-11070…
Jim Manico from Manicode Security retweeted
Please read my latest Forbes Article and share your thoughts. I share my journey on helping to scale and navigate "Security: Series C To NYSE IPO And OCC Chartered National Trust Bank"
forbes.com/councils/forbeste…
These milestones were collective achievements, made possible by dedicated colleagues and leaders across @BitGo . I remain grateful to @mikebelshe and all my colleagues for the opportunity to have contributed to the journey.
I know there is more to come!
@NYSE
@USOCC
#Fintech #Banking #DigitalAssets
I'm going to be on a podcast tomorrow with @Veracode and the OG himself, @WeldPond
Please join us!
veracode.com/resources/webin…
Jim Manico from Manicode Security retweeted
We are always so grateful for our sponsor, @Xbow!
XBOW Built a Chrome Full-Chain Exploit Affecting a Billion Users in Six Days
XBOW researchers and GPT-5.6 Sol discovered and built a Chrome full-chain exploit in less than a week, showing how an attacker could use Chrome to remotely take over a Windows machine.
The breakthrough highlights how the cost and time of finding serious vulnerabilities are falling fast, for attackers and defenders alike.
Get details on the exploit and what it means.
xbow.com/blog/xbow-built-a-c…
Jim Manico from Manicode Security retweeted
Replying to @mattjay @anton_chuvakin
Many small businesses run php sites as they lack dev teams. The people saying people deserve it likely have limited (living in a bubble) real world experience.
Jim Manico from Manicode Security retweeted
Is the #Breachpocalypse here yet?
Asking for a friend.
Jim Manico from Manicode Security retweeted
NSA, NIST and CISA published voluntary practices for preparing for, detecting, responding to and recovering from rogue AI agent incidents. The guidance addresses autonomous agents but excludes adversarial activity such as prompt injection and malware.
cyber.hendryadrian.com/artic…
Jim Manico from Manicode Security retweeted
"Hardly any impact".
"Under 1% of our revenues".
"No systems were breached"
Jim Manico from Manicode Security retweeted
Vibe coding has created a security epidemic.
(And I’m partially to blame)
When we launched GitHub Copilot in 2021, it combined GPT’s code generation with GitHub’s data. It could auto-complete a function from just its docstring.
5 years on, AI coding agents are orders of magnitude more powerful. Now a single prompt can send Astra or Fable off to write 1000s of lines of code without human intervention.
These models are trained on public source code, which doesn’t follow secure coding best practices. They generate more vulnerabilities than seasoned professionals would. Almost half of AI-written code fails basic security tests.
If you're shipping AI-written code, here's what I'd do:
1. Embed secure coding in your agents.
Don't leave it to each developer to remember. Write your secure coding requirements into the prompts every coding agent in your org runs with. Then review AI-written code with the same rigor as human-written code.
2. Closely scrutinize access controls.
AI is getting better at avoiding textbook bugs. Where it still struggles is your business logic: who should see what, and who can do what.
We recently tested an app where users upload documents for AI analysis. Nobody told the AI the documents should be private, so every user could see everyone else's…
3. Runtime testing at the speed you ship.
If agents write code around the clock, an annual pentest is not enough. Security testing has to be continuous and automated.
4. Assume attackers are already deploying autonomous attacks.
They won't tell you what they find. You need to find it first.
I love this guy. This is exactly why I built manicode.ai. Skills and context to get your AI to write secure code up front!
It’s a whole new product category.
“Secure Coding Intelligence”
cc @ronperris
Vibe coding has created a security epidemic.
(And I’m partially to blame)
When we launched GitHub Copilot in 2021, it combined GPT’s code generation with GitHub’s data. It could auto-complete a function from just its docstring.
5 years on, AI coding agents are orders of magnitude more powerful. Now a single prompt can send Astra or Fable off to write 1000s of lines of code without human intervention.
These models are trained on public source code, which doesn’t follow secure coding best practices. They generate more vulnerabilities than seasoned professionals would. Almost half of AI-written code fails basic security tests.
If you're shipping AI-written code, here's what I'd do:
1. Embed secure coding in your agents.
Don't leave it to each developer to remember. Write your secure coding requirements into the prompts every coding agent in your org runs with. Then review AI-written code with the same rigor as human-written code.
2. Closely scrutinize access controls.
AI is getting better at avoiding textbook bugs. Where it still struggles is your business logic: who should see what, and who can do what.
We recently tested an app where users upload documents for AI analysis. Nobody told the AI the documents should be private, so every user could see everyone else's…
3. Runtime testing at the speed you ship.
If agents write code around the clock, an annual pentest is not enough. Security testing has to be continuous and automated.
4. Assume attackers are already deploying autonomous attacks.
They won't tell you what they find. You need to find it first.
Jim Manico from Manicode Security retweeted
About 14 years ago. We had applied for a tender to run a full penetration test on an Indian bank. Black box. 120 IPs. External.
I don’t remember how much we quoted. But the winning bid was INR 25000 ($250 in today’s terms)
eMudhra and its “independent security verification” and “stringent audit requirements” are likely a result of similar procurement practices.
Is the #Breachpocalypse here yet?
Asking for a friend.


























