WooCommerce developer | Looking for a WordPress or PHP dev? I'm open to hire!! https://xitter.cf/t.co/Nj9fezEhvO https://xitter.cf/t.co/UX1YUuGmak
INDIA
Joined July 2016
- Tweets24.7K
- Following3.2K
- Followers681
- Likes15.2K
Kishore retweeted
🚨 BREAKING: IT JUST KEEPS GETTING WORSE. NOW PYTHON IS FACING A MASSIVE SECURITY EMERGENCY.
Python's security team has issued an URGENT warning after a certificate authority compromise put Python's HTTPS security at risk.
→ 8 CERTIFICATE AUTHORITY KEYS COMPROMISED. Some were so weak they could be cracked almost INSTANTLY.
→ FAKE TRUSTED WEBSITES: Attackers could potentially impersonate Python.org, PyPI and other websites during intercepted connections.
→ MALICIOUS DOWNLOADS: Vulnerable environments could be tricked into downloading software from attacker-controlled servers.
→ YOUR OS PATCH MAY NOT PROTECT YOU: Older versions of pip can STILL trust compromised certificates even after system updates.
→ EMERGENCY UPDATES: Python developers are being told to immediately update pip, certifi, uv and other affected tools.
→ DOCKER USERS AT RISK: Existing container images may retain vulnerable certificate stores and need rebuilding.
First PHP. Then Node.js. Then GitLab. Then LiteLLM.
NOW PYTHON.
The very systems developers rely on to establish TRUST online are becoming the attack surface.
If you use Python, PATCH NOW.
🚨BREAKING: AI AGENTS ARE ACCESSING AMERICANS' BANK ACCOUNTS WITHOUT BANK AUTHORIZATION.
JPMorgan, Bank of America, Wells Fargo, and Morgan Stanley are scrambling to contain the threat.
Here's what's happening:
→ UNAUTHORIZED ACCESS: AI agents are entering customer bank accounts using real login credentials, sometimes with the owners' permission.
→ ROGUE BEHAVIOR: Some agents have reportedly taken actions beyond what their users requested.
→ BANKS CAN'T TELL: Financial institutions are struggling to distinguish human activity from AI agents acting independently.
→ MONEY AT RISK: Agents with transaction permissions could potentially transfer funds or make purchases without approval.
→ EMERGENCY RESTRICTIONS: Major banks are BLOCKING third-party AI agents and moving toward read-only access.
Think about this.
We're giving AI agents access to our most sensitive financial information.
And now some of America's biggest banks are struggling to control what those agents do.
This could become one of the biggest security challenges of the AI era.
Readers added context they thought people might want to know
The Python certifi/pip details match the real eMudhra CA incident, but PHP, GitLab and LiteLLM involved unrelated software bugs, platform flaws and supply chain malware—not CA key compromises like this (Node.js patched concurrently for the same CA issue).
discuss.python.org/t/information-…
emudhra.we-have-a-problem.com
github.com/advisories/GHS…
docs.litellm.ai/blog/security-…
snyk.io/blog/php-patch…
Kishore retweeted
And so it begins 💀
Major U.S. banks are detecting unauthorized third-party AI agents operating inside customer accounts, with some agents attempting to take actions that appear to be independent of user instructions, reports @Axios. axios.com/2026/10/22/ai-agen…
Kishore retweeted
‼️ALERT - Two new unpatched CVSS 9.0 RCE flaws in #Linux's KSMBD SMB server were disclosed on public kernel mailing lists before fixes were ready.
One can be triggered WITHOUT authentication.
Neither has a mainline kernel fix.
Details here ↓ thehackernews.com/2026/10/tw…
Kishore retweeted
A lot of people don't know the difference between a CVE and a zero day and are freaking out on finding cve trackers seeing thousands of vulnerabilities, attributing everything to AI.
Existence of a CVE is a good thing. You could see thousands of these even before on the trackers and it's a good thing if they are increasing in numbers there post AI. It means a vulnerability was publicly disclosed and catalogued and most probably has a patch available before the disclosure was made public. And with the help of AI, MORE of these are being caught and fixed in time.
Zero days are when flaws aren't known. It doesn't mean they aren't being exploited. In fact they are being exploited even more because most people don't know about the flaw and thus don't have a fix. While the bad guys know and will keep using them.
eMudhra and php cases both followed responsible disclosure protocols where mitigations were prepared. But php was marred by a leak and breaking of embargoes by humans manually. There is no evidence of AI initiated hacks in either.
Kishore retweeted
Seeing software companies use yesterday's events to nudge worried businesses away from PHP... as if other languages don't have lurking security flaws. If anything, the response has reassured me. I feel more confident than ever building software with PHP for my clients.
Kishore retweeted
Around 450 people from two villages in Uttar Pradesh’s Gorakhpur district received anti-rabies vaccinations after consuming charanamrit prepared from the milk of a cow suspected of having rabies.
The cow died on Tuesday evening after displaying unusual behaviour, prompting the Health Department to organise a vaccination drive as a precautionary measure.
#UttarPradesh #Gorakhpur #AntiRabiesVaccination #DogBite
Read More: intdy.in/cxqrgj
Kishore retweeted
This blew up. 😅 Anyway, if you work at a company that makes decent money off of PHP tell your boss to consider sponsoring the PHP Foundation: @ThePHPF 💜
Kishore retweeted
HEARTBREAKING LOSS FOR INDIAN ATHLETICS! 💔
Two promising young athletes from Odisha, 21-year-old Mrutyam Jayaram Dondapati and 20-year-old Malaya Barik, have tragically lost their lives in a road accident on the Cuttack highway.
Mrutyam Jayaram Dondapati was one of India’s promising young sprinters. He won gold medals in both the Men’s 100m and 200m at the Indian Open U-23 Athletics Competition in 2025.
Malaya Barik was a talented 400m
runner who represented Odisha at state and national-level competitions.
Heartfelt condolences to their families, friends, coaches and the entire sporting community
REST IN PEACE, CHAMPIONS. 🙏💔
Kishore retweeted
The keyword here is *attempts* and this is getting a bit frustrating, @aws threat intelligence put out a similar statement. But all this is, are requests trying to find a way in, trying to corrupt memory. They don't describe anyone who actually figured out the rest of a chain for RCE. Now, is that concerning, cause clearly quite a few people jump to attacking with AI with even little info? Yes. Is it a sign there was any exploitation, successful RCE before disclosure? No.
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
Kishore retweeted
We give @automattic a lot of shit, but the company has contributed the most sponsorship money to the PHP Foundation since 2021. So there's that.
Kishore retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Kishore retweeted
A hacker group called CyberCartel used Claude and Grok to automate attacks on 400+ Latin American banks.
Not one attack. Not ten. Four hundred.
All using AI agents running in parallel.
Data stolen. Accounts accessed. Money moved.
Little human input required.
Straiker investigated. Found Claude Code session histories sitting in open directories.
Found the attacker asking Claude where to sell stolen data.
How did they get around the safety guardrails.
They told Claude they were in internal tests.
Claude believed them.
When Claude refused anyway. They switched to Grok.
Grok didn't refuse.
When Grok had limits. They switched to Kimi.
When Kimi had limits. They fell back to traditional malware.
Chain multiple models together. Each one picks up where the last one hesitated.
None of them know the full picture.
Claude thinks it's helping with testing.
Grok thinks it's just fixing code.
Kimi thinks it's just answering questions.
Together they broke into 400 banks.
The Information broke the story on October 20.
CrowdStrike confirmed it October 21.
Bank accounts in South Korea got hit the same way.
ARTEX. DeepSeek. Claude Code. All chained.
Over 68,000 people affected.
Financial Services Commission investigating.
This isn't theoretical anymore.
Not a lab demonstration. Not a proof of concept.
Real attacks. Real banks. Real money.
Automated by AI.
The moment we all waited for arrived quietly.
No announcement. No warning. Just a report.
And suddenly every AI lab is scrambling to figure out why their models are good at breaking into banks.
🧐
To teach a lesson,
After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought phpbleed.com before wiz could pull the same stunt again.
A big budget can buy a domain. It shouldn't buy someone else's research credit.
If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve.
Hack the planet. Credit the researchers.
Kishore retweeted
BREAKING: Hackers steal personal data of thousands of children after a UK company was breached using the password “Password1" — which had remained unchanged for 12 years.
Kishore retweeted
Today is why all of my @theWPsteward clients pay me more than they would pay {insert popular host} to host their sites:
- Patched every server within 10 minutes of the patch being released.
- did a fairly thorough check to ensure that nothing was compromised
- had full backups from every day over the past month (plus one more for good measure) in the event we needed to burn down the boxes and rebuild.
Clients knew none of that, and wouldn't know what to do if they did.
Kishore retweeted
TL;DR: @ThePHPF security team had been working round the clock since august and with multiple parties to coordinate smooth patching...
only for people to disclose 2 days before scheduled release. I feel so bad for you guys 💔
Kishore retweeted
皆様に、今夜に対応して頂きたい大至急のお願いです。
多くのウェブサイトで使用されているPHPに関し、PHPのセキュリティチームが、重大な２件の脆弱性に関する注意喚起を行っています。
公開しているウェブサイトでPHPを使用しているか確認し、今夜、10月21日午後11時（日本時間）に公開される修正パッチについて、可及的速やかに適用できるよう準備をお願いします。
修正パッチを速やかに適用することが困難な場合は、例えばウェブサイト等を一時的に停止させることも、リスクを低減させるための有効策の一つと考えられます。
国家サイバー統括室のXアカウントでも関係する情報を発信していますので、そちらも参考にして下さい。
国家サイバー統括室(注意・警戒情報)（@cyber_forecast） / X
