Archive

News on 27 Oct 2026

Calendar: October 2026

Published this day

Updated this day

  • Plan this weekAccount takeoverUpdated

    Stolen Microsoft 365 sessions hit 79 organizations: MFA alone did not stop it

    Huntress reports a 10-week campaign that replayed stolen Microsoft 365 sign-in sessions to take over mailboxes, then replaced the MFA methods. Here is what to check in your own account today.

    A related Kaspersky warning: legitimate Microsoft sign-in pages are being used as the bridge in phishing. In a press release of 22 Jul 2026 Kaspersky describes a campaign where a link led to a real Microsoft page and the victim was asked to enter a one-time code, which handed the attacker a signed-in session even after MFA. Kaspersky advises disabling the device code flow if you do not need it. Separately, Spanish-language and Indonesian press reports say Kaspersky saw more than 31,000 emails between 1 Aug and 18 Sep that linked to real Microsoft services and sent victims on to attacker pages, with lures such as "update your credentials" or "sign this document". We have not read Kaspersky's own report on that second campaign, so treat its figures as press-reported. Our advice, not Kaspersky's: a link on a Microsoft domain is not proof the destination is safe, so look at where a sign-in or consent page leads, never enter a code someone else gave you, and review which apps have access to your account.

  • A poisoned LiteLLM release stole cloud and AI keys: check if you installed it

    On 21 Oct 2026 an attacker published a malicious LiteLLM 1.107.0 to PyPI and Docker. It steals cloud credentials and AI provider keys. Here is who is affected and exactly what to do.

    LiteLLM published its root cause analysis on 23 Oct and says some earlier assumptions were inaccurate. According to the company: on 27 May a config file with the master key of an internal LiteLLM platform was committed to a public repository and the key was never revoked. On 10 Oct the attacker used it, and one API response contained the GitHub CLI token of an organisation owner. With it they pushed CI workflows that sent repository secrets, including two maintainers' tokens, to an external endpoint. On 21 Oct they pointed the release workflow at a lookalike fork, a stolen maintainer token approved the production step, and the packages went out around 11:40 UTC. The first token came from that API, not from logs as LiteLLM first suspected. LiteLLM still advises pinning 1.106.2 and says the Docker tags latest, main-latest and main-stable were repointed to clean images at 14:20 UTC. For a small team the lesson is simple: a key committed to a public repository stays valid until you revoke it, so deleting the file is not enough.

  • Act nowVulnerabilitiesUpdated

    Plex2Shell: four Plex Media Server flaws are being exploited

    CISA added four Plex Media Server flaws to its list of exploited vulnerabilities on 20 Oct 2026. Press reports say attackers install crypto miners. What to check, even if you never use Plex.

    Plex's own advisory now confirms it, and gives the exact build. A post dated 19 Oct says the flaws are "actively and widely exploited" and that Plex Media Server 1.43.3.10861 and later are not affected, so that is the number to look for (Settings, General). For servers older than that and reachable from the internet, Plex tells owners to look for unfamiliar processes, unknown .so or .dll files in the Codecs folder, connections to proxystream.st and high CPU use while idle. If you find signs, or cannot rule them out, rebuild from a clean install, clear the Codecs folder, check Preferences.xml for unexpected transcoder options, sign out all devices and change your Plex password. If you do not need remote access, turn it off and do not forward port 32400.

  • Railway says customer secrets may have been exposed: rotate them now

    On 21 Oct 2026 Railway said an unauthorized party may have accessed customer environment variables, some in decrypted form. Deployments are paused. Here is what to rotate and what to check.

    Railway has published a recovery guide (23 Oct). It is accepting deployments again, but commits pushed during the pause were not queued, so a service keeps running its last successful deployment until you trigger a new one. Railway revoked GitHub connections and API and CLI tokens, including project and account tokens. If builds fail, reconnect GitHub, check that the Railway GitHub app still has access to the repository, and recreate any CLI or CI token and update it in your CI secrets. The guide says nothing new about which accounts were affected or how the intruder got in.

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks