The Backdoor That Waited Nine Years
China-linked hackers replaced Linux login software with backdoored copies in 2016 — and nobody noticed until now. Plus: a Microsoft 365 AI flaw that stole emails via a real microsoft.com link, and a critical Splunk hole with no auth required.
Friday, June 5, 2026 · 5-minute read
🌐 World Intel
Researchers disclosed a flaw in Microsoft 365 Copilot (the AI assistant built into Office) that let an attacker steal a victim's emails, calendar data, and indexed files with a single click. The attack chained three bugs together, including an AI-specific weakness in how Copilot's search tool indexes your data. What made it especially sneaky: the malicious link pointed to a real microsoft.com domain, so email security tools wouldn't flag it as suspicious. Microsoft patched it silently on the backend — no user update required. The flaw is tracked as CVE-2026-42824.
Source: The Hacker NewsThe Sniper Dz phishing-as-a-service platform is running active campaigns across the Middle East and North Africa. Fake Facebook posts impersonate local politicians offering free mobile data packages and government subsidies. Victims who click are funneled through shared phishing infrastructure into credential-harvesting pages. The campaign exploits trust in government brands and the appeal of something-for-nothing offers — a classic social engineering combination that works especially well in communities where mobile data costs are a real financial concern.
Source: The Hacker NewsA China-linked group called Velvet Ant replaced legitimate copies of PAM and OpenSSH with backdoored versions. These modified programs worked perfectly as normal login software — but they also quietly recorded every credential entered at the login prompt, and accepted a hidden secret password that would silently let attackers in. Nine distinct variants were eventually found. The backdoors first appeared in 2016 and weren't discovered until this year — nearly a decade of undetected access on affected servers. The modified binaries passed routine security checks because they functioned correctly; only cryptographic file verification would have caught the swap.
Source: The Hacker News⚔️ Active Attacks
A critical flaw in Splunk Enterprise — the log monitoring software used by large organizations to watch for security events — lets anyone on the internet run code on the server with no login required. The vulnerable endpoint is part of a PostgreSQL API service with no authentication controls. An attacker who hits this endpoint can perform file operations and execute arbitrary code. What makes this especially bad: Splunk is your security watchdog. Compromising it means the attacker can read all your security logs, delete evidence of their own presence, and watch your defenders in real time.
What you can do: Patch Splunk immediately — the fix is available. If you can't patch right now, ensure your Splunk instance is not reachable from the public internet. It should never be. Use a firewall or network policy to restrict access to internal networks only.
Source: The Hacker News🔓 New Vulnerabilities
Three-bug chain in M365 Copilot allowed one-click exfiltration of emails, calendar events, and indexed files. The attack entry point was a link to a real microsoft.com subdomain, bypassing anti-phishing filters. Copilot's AI search became the data delivery mechanism.
Already patched on Microsoft's backend. No update needed — but review your connected apps at myapps.microsoft.com.
Unauthenticated remote code execution via an exposed PostgreSQL sidecar API endpoint. No credentials required. The flaw allows full file system access and code execution on the Splunk server.
Patch available. Apply immediately. Firewall Splunk from internet access as a baseline configuration — it should never be public-facing.
Not a traditional vulnerability — attackers physically replaced trusted binaries with backdoored versions. Any server running compromised PAM or OpenSSH copies allows silent access and credential theft. The attack requires prior access to plant the files but enables indefinite persistence afterward.
Verify binary integrity using package manager verification tools or cryptographic hashing. Rotate all credentials used on potentially affected servers.
🛠 New Tech
The Velvet Ant campaign highlights why file integrity monitoring matters. Tools like Tripwire, AIDE, and the open-source Sigstore project create cryptographic fingerprints of your critical system files — especially binaries like login software — and alert you the moment anything changes. Most Linux package managers also have built-in verification: rpm -V openssh or dpkg --verify openssh-server will compare installed files against what was originally packaged and flag any differences. Running either command takes under a minute. If you manage Linux servers, this is worth adding to your quarterly checklist. A single changed file hash in PAM or OpenSSH should be treated as a potential incident, not ignored.
💡 Deep Dive
Imagine your building has a security guard at the front desk who checks IDs. Everyone who works there trusts that guard completely. Now imagine that, one night, a different person sat down in that chair — one who looked and acted identical to the original — and has been checking IDs ever since. Except this person is also writing down everyone's name and badge number and passing that list to someone outside.
That's essentially what happened with the Velvet Ant Linux backdoor.
PAM — Pluggable Authentication Modules — is the component on Linux servers that handles login. When you type your username and password to connect to a Linux machine, PAM is what checks whether you are who you say you are. It's fundamental infrastructure. It runs on nearly every Linux server on the planet.
The Velvet Ant attackers didn't find a bug in PAM. They replaced it. They swapped the legitimate PAM binary — the actual program file — with a modified version that did everything the real one did, plus two extra things: it recorded every credential anyone typed into it, and it accepted a secret hardcoded password that would let the attackers in silently, without any log entry.
They did the same to OpenSSH, the software that handles remote logins over the internet. Nine different variants of the backdoors were eventually found across different servers, suggesting the attackers maintained and iterated on them over years.
Here's why this nearly impossible to detect with conventional security tools: the backdoored PAM worked correctly. It checked passwords. It denied unauthorized logins. It logged sessions exactly as expected. Every normal security check it encountered, it passed — because it was doing its real job perfectly well. The only thing that would catch it is comparing the binary file on disk against a known-good copy at the cryptographic level. Most organizations don't do that.
The practical lesson: your security tools only protect you if the tools themselves haven't been compromised. For foundational software — login systems, SSH, audit daemons — verify the files themselves, not just their behavior. And when you discover an intrusion, rotate every credential that was ever typed on the affected machine, even years back.