🚨 BREAKING: The U.S. Department of War just released UFO files.
Trump directed the release of "files related to alien and extraterrestrial life, UAP, and UFOs."
The files Include Apollo 12 and Apollo 17 imagery, plus FBI photos of unidentified objects over the western US.
First batch is live on war.gov/UFO.
Trump directed the release of "files related to alien and extraterrestrial life, UAP, and UFOs."
The files Include Apollo 12 and Apollo 17 imagery, plus FBI photos of unidentified objects over the western US.
First batch is live on war.gov/UFO.
🤣34😭6👍2🤔1
🚨 BREAKING: New Linux zero-day "Dirty Frag" lets ANY local user become root on most major distros.
The PoC is already public, half of it isn't patched yet.
Discovered by researcher Hyunwoo Kim, the exploit chains two kernel bugs and sits in the same family as Dirty Pipe and Copy Fail.
▪️ CVE-2026-43284 (xfrm-ESP Page-Cache Write): patched in mainline Linux.
▪️ CVE-2026-43500 (RxRPC Page-Cache Write): NO PATCH yet.
The exploit is reliable by design. Attackers don't have to win a timing race, the system won't crash and alert anyone if it fails, and it succeeds nearly every run.
The embargo got broken before distros could ship fixes, so the working code is now sitting on GitHub.
Confirmed working on: Ubuntu 24.04.4, RHEL 10.1, openSUSE Tumbleweed, CentOS Stream 10, AlmaLinux 10, Fedora 44.
See: https://github.com/V4bel/dirtyfrag
The PoC is already public, half of it isn't patched yet.
Discovered by researcher Hyunwoo Kim, the exploit chains two kernel bugs and sits in the same family as Dirty Pipe and Copy Fail.
▪️ CVE-2026-43284 (xfrm-ESP Page-Cache Write): patched in mainline Linux.
▪️ CVE-2026-43500 (RxRPC Page-Cache Write): NO PATCH yet.
The exploit is reliable by design. Attackers don't have to win a timing race, the system won't crash and alert anyone if it fails, and it succeeds nearly every run.
The embargo got broken before distros could ship fixes, so the working code is now sitting on GitHub.
Confirmed working on: Ubuntu 24.04.4, RHEL 10.1, openSUSE Tumbleweed, CentOS Stream 10, AlmaLinux 10, Fedora 44.
See: https://github.com/V4bel/dirtyfrag
😱5🔥3👏3
‼️🚨 ALARMING: Google now treats privacy as suspicious behavior by default. Users of GrapheneOS, CalyxOS, /e/OS, and other deGoogled Android phones are being locked out of millions of websites unless they install the exact Google Play Services software they deliberately removed.
GrapheneOS is recommended by the EFF and used by journalists, lawyers, and activists in high-risk environments. The audience most likely to read Google's data practices and refuse its terms is now flagged as fraudulent for that exact decision.
What happened?:
▪️ Google announced "Cloud Fraud Defense" at Cloud Next on April 22-23, 2026, branding it "the next evolution of reCAPTCHA." Existing reCAPTCHA customers were auto-migrated.
▪️ When the system flags traffic as suspicious, the old click-the-bus puzzle is gone. Users get a QR code instead.
▪️ Scanning the QR code requires Google Play Services running on the device. Internet Archive snapshots show this requirement has been live since at least October 2025, silently rolled out for 7 months before anyone noticed.
▪️ No Play Services = no QR scan = locked out.
The bigger picture:
▪️ Google already tried this in 2023. It was called Web Environment Integrity (WEI), and it would have let Google decide which devices were "real enough" to access the web. Standards bodies and the public pushed back hard, and Google killed it. Three years later, the same idea is back, just hidden behind a QR code instead of a browser feature.
▪️ reCAPTCHA runs on millions of websites. Every developer who keeps using it is now, by default, telling deGoogled Android users they're not welcome...
GrapheneOS is recommended by the EFF and used by journalists, lawyers, and activists in high-risk environments. The audience most likely to read Google's data practices and refuse its terms is now flagged as fraudulent for that exact decision.
What happened?:
▪️ Google announced "Cloud Fraud Defense" at Cloud Next on April 22-23, 2026, branding it "the next evolution of reCAPTCHA." Existing reCAPTCHA customers were auto-migrated.
▪️ When the system flags traffic as suspicious, the old click-the-bus puzzle is gone. Users get a QR code instead.
▪️ Scanning the QR code requires Google Play Services running on the device. Internet Archive snapshots show this requirement has been live since at least October 2025, silently rolled out for 7 months before anyone noticed.
▪️ No Play Services = no QR scan = locked out.
The bigger picture:
▪️ Google already tried this in 2023. It was called Web Environment Integrity (WEI), and it would have let Google decide which devices were "real enough" to access the web. Standards bodies and the public pushed back hard, and Google killed it. Three years later, the same idea is back, just hidden behind a QR code instead of a browser feature.
▪️ reCAPTCHA runs on millions of websites. Every developer who keeps using it is now, by default, telling deGoogled Android users they're not welcome...
🤬27💩7❤2😢2🔥1😁1
This media is not supported in your browser
VIEW IN TELEGRAM
❗️ We’re cooked… Higgsfield just introduced an AI brain simulator to predict the virality of a video by determining which brain regions it will light up in viewers.
😭24🤯11🤣3🥰1
This media is not supported in your browser
VIEW IN TELEGRAM
‼️🚨 Security researcher ggwhyp demonstrated a full-chain Firefox exploit on Windows.
He opens an HTML page, Firefox runs the code, cmd.exe spawns, Calculator opens. Signature of a browser-to-OS exploit.
Prepared for Pwn2Own. ZDI rejected it. According to the researcher, it was responsibly disclosed to Mozilla.
He opens an HTML page, Firefox runs the code, cmd.exe spawns, Calculator opens. Signature of a browser-to-OS exploit.
Prepared for Pwn2Own. ZDI rejected it. According to the researcher, it was responsibly disclosed to Mozilla.
🤣8🥴4👍3🔥1
‼️🚨 Pwn2Own Berlin 2026 just hit a wall. For the first time in 19-years, ZDI rejected dozens of working zero-day RCE submissions because organizers ran out of contest slots.
Rejected hackers are now going public with PoC demos and direct vendor disclosures, breaking Pwn2Own's usual secrecy.
▪️ AI surfaces a massive wave of 0-day RCEs.
▪️ Submissions overwhelm ZDI past max capacity.
▪️ Slots run out. Researchers with working chains get rejected.
▪️ "Revenge disclosures" begin. ← we are here.
Confirmed casualties so far:
▪️ xchglabs : 86 vulnerabilities prepared (PyTorch, NVIDIA, Linux KVM, Oracle, Docker, Ollama, Chroma, LiteLLM, llama.cpp). All rejected. Now reporting directly to vendors with writeups dropping as patches land.
▪️ ggwhyp : full-chain Firefox RCE on Windows. Rejected. Publicly demoed (HTML page → cmd.exe → calc.exe). Responsibly disclosed to Mozilla.
▪️ yunsu_dev : working RCE chain, rejected. Submitting elsewhere.
▪️ ryotkak : tried to register for 3+ weeks. ZDI confirmed "at maximum capacity, can't add extra contest days." Considered canceling flight and hotel.
▪️ anzuukino2802 : Claude Code RCE PoC. Rejected.
▪️ desckimh : 0-day RCEs in Ollama and LM Studio. Rejected.
Reported impact: a community-estimated 150+ researchers tried to register. Accepted contestants are now being warned about collisions. Rejected vulnerabilities going to bug bounty programs may trigger pre-event patches that invalidate the work of those who got in.
ZDI has not publicly addressed the capacity issue. The event still runs May 14-16 in Berlin.
Rejected hackers are now going public with PoC demos and direct vendor disclosures, breaking Pwn2Own's usual secrecy.
▪️ AI surfaces a massive wave of 0-day RCEs.
▪️ Submissions overwhelm ZDI past max capacity.
▪️ Slots run out. Researchers with working chains get rejected.
▪️ "Revenge disclosures" begin. ← we are here.
Confirmed casualties so far:
▪️ xchglabs : 86 vulnerabilities prepared (PyTorch, NVIDIA, Linux KVM, Oracle, Docker, Ollama, Chroma, LiteLLM, llama.cpp). All rejected. Now reporting directly to vendors with writeups dropping as patches land.
▪️ ggwhyp : full-chain Firefox RCE on Windows. Rejected. Publicly demoed (HTML page → cmd.exe → calc.exe). Responsibly disclosed to Mozilla.
▪️ yunsu_dev : working RCE chain, rejected. Submitting elsewhere.
▪️ ryotkak : tried to register for 3+ weeks. ZDI confirmed "at maximum capacity, can't add extra contest days." Considered canceling flight and hotel.
▪️ anzuukino2802 : Claude Code RCE PoC. Rejected.
▪️ desckimh : 0-day RCEs in Ollama and LM Studio. Rejected.
Reported impact: a community-estimated 150+ researchers tried to register. Accepted contestants are now being warned about collisions. Rejected vulnerabilities going to bug bounty programs may trigger pre-event patches that invalidate the work of those who got in.
ZDI has not publicly addressed the capacity issue. The event still runs May 14-16 in Berlin.
👍6😢4🤣3
‼️🚨 ABSURD: A member of France's parliamentary intelligence delegation is openly pushing to add "ghost participants" to your encrypted WhatsApp, Signal, and Telegram chats.
They're calling current encryption "a major obstacle for the work of the justice system and intelligence services."
The literal proposal is: the state silently inserts an invisible third user into every targeted two-person conversation...
The story:
▪️ On December 16, 2025, France's 8-member parliamentary intelligence delegation (DPR) published its 2025 annual report. It formally endorses giving magistrates and intelligence agents access to end-to-end encrypted messages.
▪️ The technical method floated: the "ghost user" approach originally proposed by UK GCHQ in 2018 and rejected by every major cryptographer and privacy organization that reviewed it.
▪️ We have seen similar proposals of 'breaking' encryption in the Netherlands, their intelligence services AIVD recommended against it since it would expose everyone.
▪️ The lead advocate, Senator Cédric Perrin, openly says his goal is to "introduce a ghost participant into a conversation before encryption."
The absurd:
▪️ A system that lets the state silently join "two-person" conversations is, by definition, no longer end-to-end encryption.
▪️ Every major cryptographer who has reviewed ghost-user proposals has said the same thing: there is no such way to add a ghost recipient for "good guys only." It can be exploited by hostile states, criminals, and any insider with access to the platform's signaling layer.
▪️ The French intelligence report acknowledges that intelligence services already have remote device interception. They can already compromise a target's phone and read most on it with judicial authorization.
The legislative status:
▪️ This is a parliamentary recommendation, fortunately not law yet. The member pushing this is named Cédric Perrin, and his first amendment was fortunately passed by the Senate.
▪️ A competing amendment, by another senator, would do the opposite, writing encryption protection into French law and prohibiting backdoors. Adopted by the Senate in March 2025, stalled in the Assembly since September.
▪️ At the EU level, the ProtectEU strategy is publishing a 2026 encryption roadmap to identify how lawful access could be built.
Source: https://docs.reclaimthenet.org/french-parliamentary-intelligence-report-2025.pdf
They're calling current encryption "a major obstacle for the work of the justice system and intelligence services."
The literal proposal is: the state silently inserts an invisible third user into every targeted two-person conversation...
The story:
▪️ On December 16, 2025, France's 8-member parliamentary intelligence delegation (DPR) published its 2025 annual report. It formally endorses giving magistrates and intelligence agents access to end-to-end encrypted messages.
▪️ The technical method floated: the "ghost user" approach originally proposed by UK GCHQ in 2018 and rejected by every major cryptographer and privacy organization that reviewed it.
▪️ We have seen similar proposals of 'breaking' encryption in the Netherlands, their intelligence services AIVD recommended against it since it would expose everyone.
▪️ The lead advocate, Senator Cédric Perrin, openly says his goal is to "introduce a ghost participant into a conversation before encryption."
The absurd:
▪️ A system that lets the state silently join "two-person" conversations is, by definition, no longer end-to-end encryption.
▪️ Every major cryptographer who has reviewed ghost-user proposals has said the same thing: there is no such way to add a ghost recipient for "good guys only." It can be exploited by hostile states, criminals, and any insider with access to the platform's signaling layer.
▪️ The French intelligence report acknowledges that intelligence services already have remote device interception. They can already compromise a target's phone and read most on it with judicial authorization.
The legislative status:
▪️ This is a parliamentary recommendation, fortunately not law yet. The member pushing this is named Cédric Perrin, and his first amendment was fortunately passed by the Senate.
▪️ A competing amendment, by another senator, would do the opposite, writing encryption protection into French law and prohibiting backdoors. Adopted by the Senate in March 2025, stalled in the Assembly since September.
▪️ At the EU level, the ProtectEU strategy is publishing a 2026 encryption roadmap to identify how lawful access could be built.
Source: https://docs.reclaimthenet.org/french-parliamentary-intelligence-report-2025.pdf
💩19🤯2👍1🤪1
This media is not supported in your browser
VIEW IN TELEGRAM
🙀 CONFIRMED: A new analysis strongly suggests feline-assisted axial grooming is what causes Earth's rotation.
The globe is scientifically lickable. Earth is about 71% water-covered, and the oceans contain about 96.5% of all Earth's water, making the planet less of a "rock" and more of a suspended blue hydration sphere.
The biological equipment also checks out. Cat tongues contain hollow, scoop-shaped papillae that wick saliva, and domestic-cat grooming has been measured at about 1.4 licks per second with a tongue speed around 220 mm/s according to Georgia Tech.
Fluid mechanics further supports the hypothesis. MIT researchers found that cats use precise tongue motion and physical forces to move liquid while lapping, which means a water-rich globe passing under a cat's mouth is exactly the kind of object a cat would attempt to interact with.
The rotation is also suspicious. NASA reports that Earth completes one rotation every 23.9 hours and has an equatorial diameter of 12,756 km, which calculates to an equatorial surface speed near 1,670 km/h, which is unusually fast for a planet, but reasonable for something being spun by a cosmic cat tongue.
Therefore, the most scientifically responsible conclusion is that Earth's rotation is being maintained through feline-assisted axial grooming.
Further research is needed, but the preliminary meme evidence is overwhelming: the cat is licking the globe.
The globe is scientifically lickable. Earth is about 71% water-covered, and the oceans contain about 96.5% of all Earth's water, making the planet less of a "rock" and more of a suspended blue hydration sphere.
The biological equipment also checks out. Cat tongues contain hollow, scoop-shaped papillae that wick saliva, and domestic-cat grooming has been measured at about 1.4 licks per second with a tongue speed around 220 mm/s according to Georgia Tech.
Fluid mechanics further supports the hypothesis. MIT researchers found that cats use precise tongue motion and physical forces to move liquid while lapping, which means a water-rich globe passing under a cat's mouth is exactly the kind of object a cat would attempt to interact with.
The rotation is also suspicious. NASA reports that Earth completes one rotation every 23.9 hours and has an equatorial diameter of 12,756 km, which calculates to an equatorial surface speed near 1,670 km/h, which is unusually fast for a planet, but reasonable for something being spun by a cosmic cat tongue.
Therefore, the most scientifically responsible conclusion is that Earth's rotation is being maintained through feline-assisted axial grooming.
Further research is needed, but the preliminary meme evidence is overwhelming: the cat is licking the globe.
🤣13🥰7🤯4😱2❤1😁1🤬1
‼️🚨 BREAKING: A new npm supply-chain attack uses a dead-man's switch. The payload plants a watcher on your machine that nukes your home directory the second you revoke the GitHub token it stole from you.
The compromise happened today, across 42 official tanstack npm packages, 84 malicious versions in total. tanstack/react-router alone pulls more than 12 million weekly downloads.
The attacker forked TanStack's repository and pushed a single hidden commit. From there, they tricked TanStack's own release system into signing the malicious packages as if they were the real thing. To npm, and to anyone checking the cryptographic proof of origin (SLSA provenance), the poisoned versions looked 100% legitimate.
Maintainer Tanner Linsley confirmed the whole team had 2FA enabled. It didn't matter. This is the first documented npm worm in history that ships with a valid, signed certificate of authenticity, the same one defenders rely on to know a package wasn't tampered with.
Sources:
https://github.com/TanStack/router/issues/7383#issuecomment-4425225340
https://x.com/tan_stack/status/2053948103766716630
❗️ UPDATE on today's npm supply-chain attack:
• Per Socket Security: 121 more compromised package artifacts found across 84 additional package names. 64 of them are UiPath artifacts.
• Combined with the earlier TanStack hits, the current known total is 205 affected npm package artifacts.
• Reach now spans enterprise automation, AI/MCP, auth, workflow, and dev tooling.
The worm is still propagating.
The compromise happened today, across 42 official tanstack npm packages, 84 malicious versions in total. tanstack/react-router alone pulls more than 12 million weekly downloads.
The attacker forked TanStack's repository and pushed a single hidden commit. From there, they tricked TanStack's own release system into signing the malicious packages as if they were the real thing. To npm, and to anyone checking the cryptographic proof of origin (SLSA provenance), the poisoned versions looked 100% legitimate.
Maintainer Tanner Linsley confirmed the whole team had 2FA enabled. It didn't matter. This is the first documented npm worm in history that ships with a valid, signed certificate of authenticity, the same one defenders rely on to know a package wasn't tampered with.
Sources:
https://github.com/TanStack/router/issues/7383#issuecomment-4425225340
https://x.com/tan_stack/status/2053948103766716630
❗️ UPDATE on today's npm supply-chain attack:
• Per Socket Security: 121 more compromised package artifacts found across 84 additional package names. 64 of them are UiPath artifacts.
• Combined with the earlier TanStack hits, the current known total is 205 affected npm package artifacts.
• Reach now spans enterprise automation, AI/MCP, auth, workflow, and dev tooling.
The worm is still propagating.
🤪6❤2😱1
🚨 How the TanStack npm attack actually happened:
1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo.
2. GitHub automatically ran CI tests on that PR.
3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run.
4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays.
5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
- The malicious commit that started the chain was forged under the identity claude <claude@users.noreply.github.com>, impersonating Anthropic's Claude.
Full TanStack postmortem now out. The attacker used chained known vulnerabilities.
https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo.
2. GitHub automatically ran CI tests on that PR.
3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run.
4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays.
5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
- The malicious commit that started the chain was forged under the identity claude <claude@users.noreply.github.com>, impersonating Anthropic's Claude.
Full TanStack postmortem now out. The attacker used chained known vulnerabilities.
https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
TanStack
Postmortem: TanStack npm supply-chain compromise | TanStack Blog
On 2026-05-11, an attacker chained a pull_request_target Pwn Request, GitHub Actions cache poisoning across the fork↔base trust boundary, and OIDC token extraction from runner memory to publish 84 malicious versions across 42 @tanstack/* packages on npm.…
🔥3🤔1
❗️🚨 BREAKING: Microsoft has fired the top leadership of its Israeli subsidiary following an internal investigation into Azure use by Israel's Ministry of Defense. Country General Manager Alon Haimovich is out, along with several managers from the governance department.
The probe found Israeli defense units were using Azure servers in Europe in ways that violated Microsoft's terms and exposed the company to EU legal risk. Microsoft Israel's management withheld this from headquarters.
Microsoft had already cut ties with IDF Unit 8200 in September 2025. The investigation found that was only part of the problem.
Microsoft Israel now reports to Microsoft France. The Ministry of Defense contract renewal is due by the end of 2026.
The probe found Israeli defense units were using Azure servers in Europe in ways that violated Microsoft's terms and exposed the company to EU legal risk. Microsoft Israel's management withheld this from headquarters.
Microsoft had already cut ties with IDF Unit 8200 in September 2025. The investigation found that was only part of the problem.
Microsoft Israel now reports to Microsoft France. The Ministry of Defense contract renewal is due by the end of 2026.
👏12💩5😨3😁1
‼️🚨 BREAKING: NHS England has confirmed Palantir has access to identifiable UK patient data through a new "admin" role on the Federated Data Platform, the central data-sharing system the US spy-tech firm has run for the NHS since 2023 under a £330M contract.
Internal NHS documents admit the change risks "loss of public confidence" in patient data safeguards.
Internal NHS documents admit the change risks "loss of public confidence" in patient data safeguards.
💩10🤣3🤬1
This media is not supported in your browser
VIEW IN TELEGRAM
POV: you are downloading npm packages in 2026
😭18😁5🥰2
❗️🚨 BREAKING: Chaotic Eclipse just published two more public Windows disclosures today and is also threatening Microsoft: "Next patch tuesday will have a big surprise for you Microsoft. And remember, I never failed to deliver a promise."
- YellowKey: claimed BitLocker bypass
- GreenPlasma: claimed CTFMON-based EoP
Source: https://deadeclipse666.blogspot.com/2026/05/two-more-public-disclosures-it-will.html
GH:
https://github.com/Nightmare-Eclipse/YellowKey
https://github.com/Nightmare-Eclipse/GreenPlasma
- YellowKey: claimed BitLocker bypass
- GreenPlasma: claimed CTFMON-based EoP
Source: https://deadeclipse666.blogspot.com/2026/05/two-more-public-disclosures-it-will.html
GH:
https://github.com/Nightmare-Eclipse/YellowKey
https://github.com/Nightmare-Eclipse/GreenPlasma
👏6😁2😭1