โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG) header
โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG) profile picture

CSDC, IT-Security & Cloud Computing Engineering | network solutions | #Bitcoin is the future. | love cats & my gf

Wien, ร–sterreich
Joined April 2015
Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)Photo by โ€ข ๐‘ฏ๐’‚๐’๐’Š (@HaNiTLG)
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
๐Ÿšจ NOW 53 COUNTRIES ARE TELLING THEIR CITIZENS TO STOCKPILE FOR EMERGENCY. HERE IS THE FULL LIST ๐ŸŒ EUROPE (29): ๐Ÿ‡ฆ๐Ÿ‡น AUSTRIA: 10โ€“14 DAYS ๐Ÿ‡ธ๐Ÿ‡ฐ SLOVAKIA: 14 DAYS (POWER CUTS) ๐Ÿ‡ฉ๐Ÿ‡ช GERMANY: UP TO 10 DAYS ๐Ÿ‡ธ๐Ÿ‡ช SWEDEN: 1 WEEK ๐Ÿ‡ณ๐Ÿ‡ด NORWAY: 1 WEEK ๐Ÿ‡จ๐Ÿ‡ญ SWITZERLAND: 1 WEEK ๐Ÿ‡ช๐Ÿ‡ช ESTONIA: 1 WEEK ๐Ÿ‡ธ๐Ÿ‡ฎ SLOVENIA: 3 DAYS WATER, 30 DAYS FOOD ๐Ÿ‡ฌ๐Ÿ‡ง UK: 3 DAYS ๐Ÿ‡ฉ๐Ÿ‡ฐ DENMARK: 3 DAYS ๐Ÿ‡ต๐Ÿ‡ฑ POLAND: 3 DAYS ๐Ÿ‡ฌ๐Ÿ‡ท GREECE: 3 DAYS ๐Ÿ‡จ๐Ÿ‡พ CYPRUS: 3 DAYS ๐Ÿ‡ฎ๐Ÿ‡ธ ICELAND: 3 DAYS ๐Ÿ‡ซ๐Ÿ‡ท FRANCE: 72 HOURS ๐Ÿ‡ณ๐Ÿ‡ฑ NETHERLANDS: 72 HOURS ๐Ÿ‡ซ๐Ÿ‡ฎ FINLAND: 72 HOURS ๐Ÿ‡ฑ๐Ÿ‡ป LATVIA: 72 HOURS ๐Ÿ‡ฑ๐Ÿ‡น LITHUANIA: 72 HOURS ๐Ÿ‡จ๐Ÿ‡ฟ CZECHIA: 72 HOURS ๐Ÿ‡ญ๐Ÿ‡ท CROATIA: 72 HOURS ๐Ÿ‡ง๐Ÿ‡ช BELGIUM: 72 HOURS ๐Ÿ‡ฑ๐Ÿ‡บ LUXEMBOURG: 72 HOURS ๐Ÿ‡ช๐Ÿ‡ธ SPAIN: 72 HOURS ๐Ÿ‡ต๐Ÿ‡น PORTUGAL: 72 HOURS ๐Ÿ‡ท๐Ÿ‡ด ROMANIA: 72 HOURS ๐Ÿ‡ง๐Ÿ‡ฌ BULGARIA: 72 HOURS ๐Ÿ‡ฒ๐Ÿ‡ฉ MOLDOVA: 72 HOURS ๐Ÿ‡ฎ๐Ÿ‡ช IRELAND: "STOCK THE ESSENTIALS" ๐ŸŒŽ AMERICAS (9): ๐Ÿ‡ต๐Ÿ‡ช PERU: 4 DAYS ๐Ÿ‡จ๐Ÿ‡ฆ CANADA: 72 HOURS ๐Ÿ‡ฒ๐Ÿ‡ฝ MEXICO: 72 HOURS ๐Ÿ‡จ๐Ÿ‡ด COLOMBIA: 72 HOURS ๐Ÿ‡ช๐Ÿ‡จ ECUADOR: 72 HOURS ๐Ÿ‡จ๐Ÿ‡ฑ CHILE: 48โ€“72 HOURS ๐Ÿ‡บ๐Ÿ‡ธ USA: "SEVERAL DAYS" ๐Ÿ‡ง๐Ÿ‡ท BRAZIL: EMERGENCY KIT ๐Ÿ‡ฆ๐Ÿ‡ท ARGENTINA: EMERGENCY BACKPACK ๐ŸŒ ASIA (12): ๐Ÿ‡น๐Ÿ‡ผ TAIWAN: 7 DAYS ๐Ÿ‡ฏ๐Ÿ‡ต JAPAN: 3 DAYS, 1 WEEK IF POSSIBLE ๐Ÿ‡ฎ๐Ÿ‡ฑ ISRAEL: 3 DAYS ๐Ÿ‡ฐ๐Ÿ‡ฟ KAZAKHSTAN: 3 DAYS ๐Ÿ‡น๐Ÿ‡ท TURKEY: 72 HOURS ๐Ÿ‡ฌ๐Ÿ‡ช GEORGIA: 72 HOURS ๐Ÿ‡ฎ๐Ÿ‡ฉ INDONESIA: 72 HOURS ๐Ÿ‡ฒ๐Ÿ‡พ MALAYSIA: 72 HOURS ๐Ÿ‡ฐ๐Ÿ‡ผ KUWAIT: 2 DAYS ๐Ÿ‡ฎ๐Ÿ‡ณ INDIA: EMERGENCY KIT ๐Ÿ‡ต๐Ÿ‡ญ PHILIPPINES: GO BAG ๐Ÿ‡ธ๐Ÿ‡ฌ SINGAPORE: READY BAG ๐ŸŒ OCEANIA + AFRICA (3): ๐Ÿ‡ณ๐Ÿ‡ฟ NEW ZEALAND: 3+ DAYS ๐Ÿ‡ฟ๐Ÿ‡ฆ SOUTH AFRICA: 3 DAYS ๐Ÿ‡ฆ๐Ÿ‡บ AUSTRALIA: EMERGENCY KIT ๐Ÿ‡ช๐Ÿ‡บ EU: EVERY CITIZEN READY FOR 72 HOURS REASONS GIVEN: WAR. EXTREME WEATHER. CYBER ATTACKS. WHAT DO THEY KNOW THAT WE DON'T? FOLLOW ME FOR EVERY NEW COUNTRY THAT JOINS ๐Ÿ””
๐Ÿšจ GOVERNMENTS ARE TELLING CITIZENS TO STOCKPILE FOR EMERGENCY ๐Ÿ‡ฌ๐Ÿ‡ง UK: 3 DAYS ๐Ÿ‡ฏ๐Ÿ‡ต JAPAN: 3 DAYS And they are not alone: ๐Ÿ‡ง๐Ÿ‡ช Belgium: 72 HOURS ๐Ÿ‡ฎ๐Ÿ‡ช Ireland: โ€œBe Emergency Readyโ€ ๐Ÿ‡ซ๐Ÿ‡ท France: 72 HOURS ๐Ÿ‡ฉ๐Ÿ‡ช Germany: 3 to 10 DAYS ๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands: 72 HOURS ๐Ÿ‡ต๐Ÿ‡ฑ Poland: 3 DAYS ๐Ÿ‡ธ๐Ÿ‡ช Sweden: 1 WEEK ๐Ÿ‡ณ๐Ÿ‡ด Norway: 1 WEEK ๐Ÿ‡ซ๐Ÿ‡ฎ Finland: 72 HOURS ๐Ÿ‡ฉ๐Ÿ‡ฐ Denmark: 3 DAYS ๐Ÿ‡ช๐Ÿ‡ช Estonia: 1 WEEK ๐Ÿ‡ฑ๐Ÿ‡ป Latvia: 72 HOURS ๐Ÿ‡ฑ๐Ÿ‡น Lithuania: 72 HOURS ๐Ÿ‡จ๐Ÿ‡ญ Switzerland: 1 WEEK ๐Ÿ‡น๐Ÿ‡ผ Taiwan: 7 DAYS ๐Ÿ‡ช๐Ÿ‡บ EU: 72 HOURS 17 countries + the EU. What do they know that we donโ€™t? Follow me so you donโ€™t miss what comes next ๐Ÿ””
Readers added context they thought people might want to know
The viral list compiles routine longstanding preparedness recommendations for disasters rather than new synchronized warnings from governments. gov.uk/government/newโ€ฆ afad.gov.tr/afet-ve-acil-dโ€ฆ commission.europa.eu/topics/prepareโ€ฆ
679
3,376
804
11,088
2,414,810
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
Under pressure from Israeli prime minister Benjamin Netanyahu, the Trump administration may be within days of launching a nuclear strike on Iran. The target would be Pickax Mountain in central Iran, where Israeli intelligence claims the Iranian government has restarted its nuclear enrichment program. No conventional weapon in the American arsenal can penetrate 300 feet of solid granite to destroy the tunnels where enrichment is supposedly taking place. The only military option is a nuclear strike. Netanyahu has been pushing hard for one. โ€œBibi calls Trump about it every day,โ€ says an informed observer. Netanyahu is cornered and desperate. After last weekโ€™s election results, he canโ€™t form a government unless Trump intervenes directly in Israeli politics and brokers a deal with other parties that gives Netanyahu 61 seats in the Knesset. Otherwise, he is out as prime minister and on his way to ignominy, investigations and possibly jail. Netanyahu must stay close to Trump. He needs this war. To that end, heโ€™s applied maximum pressure to his closest allies in the administration, including Secretary of Defense Pete Hegseth and CENTCOM commander Brad Cooper. Both oppose a negotiated settlement to the war theyโ€™ve so grievously mismanaged; both are pushing to restart major combat operations. Secretary of State Marco Rubio and CIA director John Ratcliffe are also following Netanyahuโ€™s lead, as are leaders of the Democratic Party. In a recent meeting on the subject, former president Barack Obama said he opposes the current Iran peace deal being drafted in Doha. The rest of Americaโ€™s longtime allies in the Middle East are terrified by the prospect of more war. On September 27th, Netanyahu flew secretly to Abu Dhabi to enlist the UAE in his lobbying effort for a final attack on Iran. The Emiratis refused. After eight months of conflict, Gulf economies are teetering. So are global energy and fertilizer markets. They wonโ€™t recover soon. Globally, there are a total of about 850 supertankers used to transport oil from producers to the rest of the world. In October alone, 11 of them were badly damaged in Hormuz. At this pace, a global depression is imminent. A nuclear strike would radically accelerate the destruction. Fallout from a ground explosion at Pickax Mountain would contaminate the Persian Gulf, poisoning the water supply for 100 million people. And those are just some of the immediate consequences for the region. The rest of the world is every bit as exposed. No country other than the United States has ever used a nuclear weapon in war. Some would like to. An American nuclear attack on Iran would set a new precedent. The Russians have already told at least two other governments that an American nuclear strike on Iran would free them to use nuclear weapons against Ukraine. Pakistan and India would be tempted to do the same against each other, as would North Korea against Seoul. After the first nuclear strike, World War Three is inevitable. That war would be short and final. Weโ€™ve been sleepwalking toward this moment for months. Since February, the administration has quietly rewritten Americaโ€™s nuclear doctrine to make first use of so-called โ€œbattlefield nukesโ€ easier and therefore more likely. No one in Washington in either party seems bothered by this. Now weโ€™re on the brink of it. Close observers say Trump is likely to decide by next weekend whether or not to use nuclear weapons. That would be November 7, six days from now. To his credit, heโ€™s hesitating. At the moment, Trump is listening to his vice president, JD Vance, and to his envoy and friend Steve Witkoff, both of whom argue a deal with Iran can be made. Theyโ€™re right, though it wonโ€™t be simple. The Iranians are famously frustrating to negotiate with under any circumstances, and elements of that government have become more radical since Ayatollah Ali Khamenei and his family were killed in February. After decades of isolation, even relatively moderate Iranian leaders seem confused by how decisions are made in the West. (There is a widespread belief in Tehran, for example, that the United States government controls Israel.) But overall, people who have spoken to decision-makers in Iran say there is consensus there that more war is bad for everyone and a deal is worth making. One group that hasnโ€™t been consulted so far is the global population โ€” the hundreds of millions of people who will be killed along with their children if Trump is pushed by Netanyahu into launching a nuclear strike next week. Now would be the time for them to speak up.
29,270
75,998
26,001
399,959
94,088,414
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
โ€ผ๏ธ Ubuntu and Red Hat still have no fix for a Linux kernel flaw that Anthropic says its unreleased AI model turned into a remote root exploit. The bug, CVE-2026-98432, is a use-after-free in the IPv4 TCP handshake, rated 9.8 out of 10. The exploit needs no credentials and targets servers with a multipath TCP listener, which Go 1.24 and later open by default. The fix reached stable kernels on 11 October and Debian has shipped it. Ubuntu still marks every release from 16.04 to 26.10 vulnerable. Red Hat now rates it Critical but has no patched kernel for RHEL 8, 9 or 10. Anthropic has not released the exploit. By its count, it takes 48 minutes to leak a kernel pointer and five more to run commands as root.
77
328
73
2,436
245,710
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineerโ€™s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the companyโ€™s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annouโ€ฆ
3,419
6,179
3,765
29,651
7,185,503
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
๐Ÿ”ด CVE-2026-98432 | Linux Kernel โ€“ Critical UAF Linux รงekirdeฤŸinde TCP/IPv4 baฤŸlantฤฑ iลŸleme sรผrecini etkileyen, uzaktan istismar potansiyeline sahip bir Use-After-Free (UAF) aรงฤฑฤŸฤฑ tespit edildi. โ— CVSS 3.1: 9.8 (Critical) โ— AฤŸ รผzerinden istismar โ— Kimlik doฤŸrulama gerektirmiyor โ— Bellek gรผvenliฤŸi ve sistem kullanฤฑlabilirliฤŸi riski Sistem yรถneticileri, linux daฤŸฤฑtฤฑmlarฤฑnฤฑn gรผvenlik duyurularฤฑnฤฑ takip ederek yamalฤฑ sรผrรผmlere geรงmelidir. ubuntu.com/security/CVE-2026โ€ฆ
29
553
172
2,635
553,526
Wir haben auf Twitter einen Krieg zwischen Deutschen und Chinesen vor GTA 6โ€ฆ ๐Ÿซฉ
1
40
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
today we launched ChatGPT. try talking with it here: chat.openai.com
4,956
13,795
13,148
114,538
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
hOw Do We FiND tHe VulnErAbLE PhP SerViCeS??!!?!! seriously? nmap -sV --reason -A -vvv -p80,443,8080,8000,8443 --script http-headers,http-server-header,http-generator 10.0.1.1/24 look for X-Powered-By: PHP/version this isn't hard guys.
31
80
4
1,101
50,737
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
139
1,092
33
18,648
668,973
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
Imagine running PHP and Go on the backend, Node.js on the frontend, NGINX as the reverse proxy, Linux as the server, an HTTPS certificate from eMudhra And also deploying everything via GitLab โ˜•๏ธ
๐Ÿšจ Security vulnerabilities reported in a SINGLE day: PHP โ€” 2 CVEs Node.js โ€” 10 CVEs NGINX โ€” 5 CVEs Go โ€” 1 CVE GitLab โ€” 12 CVEs eMudhra โ€” CA certificate compromise
105
449
87
4,379
174,947
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
GitLab has patched a critical security flaw with a CVSS score of 10.0, the highest possible severity. The vulnerability, CVE-2026-110264, could allow an unauthenticated attacker to execute arbitrary code on self-managed GitLab servers. It affects GitLab versions dating back to 7.0, released in 2014. GitLab says there is currently no evidence that the flaw has been exploited, but recommends updating to a patched version as soon as possible.
11
66
8
817
33,809
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
As if PHP2Shell wasn't enough for one day... now GitLab. ๐Ÿ˜… ๐Ÿšจ CRITICAL GITLAB ALERT (CVSS 10.0) CVE-2026-110264 could allow unauthenticated RCE on self-managed GitLab servers. โš ๏ธ Potentially affects 12 years of releases, dating back to 2014. Patches available. Update immediately! docs.gitlab.com/releases/patโ€ฆ #gitlab #cybersecurity
58
533
122
4,065
297,341
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
๐Ÿšจ CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases. CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers. Read - thehackernews.com/2026/10/crโ€ฆ
263
2,848
1,546
14,869
3,574,522
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
๐Ÿšจ UPDATE: PHP 8.5.12 may still be vulnerable to php2shell! Researchers are reporting a successful double-free trigger on the newly patched release. โš ๏ธ The official fixes may be incomplete. A crash alone doesn't confirm RCE, but this deserves urgent investigation. Don't assume you're safe just because you've patched. #php4shell #php #cybersecurity nitter.gq/_annieversary/status/2โ€ฆ
chat. chat... its not funny anymore
Readers added context they thought people might want to know
The original post has since been edited to specify that this was about an unrelated vulnerability that the user had discovered, not the recently patched vulnerability. fedi.katze.sh/@elise/1174793โ€ฆ
32
572
191
1,848
927,982
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.
915
7,066
1,159
57,936
3,850,753
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
chat. chat... its not funny anymore
Readers added context they thought people might want to know
The original post has since been edited to specify that this was about an unrelated vulnerability that the user had discovered, not the recently patched vulnerability. fedi.katze.sh/@elise/1174793โ€ฆ
115
419
197
7,405
964,789
โ€ข ๐‘ฏ๐’‚๐’๐’Š retweeted
โ€ผ๏ธBREAKING: PHP has released its fix for the two leaked flaws, which can let attackers run code on servers without logging in. "There are no complete mitigations, updating is the only safe choice," PHP says. Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 now. PHP says Apache with mod_php is most at risk, with a demonstrated exploit that fires before any application code runs. PHP 8.1 and older get no official update, though PHP has published source backports for 7.4, 8.0 and 8.1.
63
969
113
4,589
256,722