Newsletter archiveSent 30 Oct 2026

Update GitLab and Tailscale, rotate OpenCode keys, and a script that drained Polymarket traders

Five things to act on this week: GitLab, Tailscale, OpenCode keys, Supabase and a script that drained Polymarket traders. Plus what to plan and what is good to know.

← All editions

Hi, here is what mattered this week, in plain English.

Act now

  • Polymarket traders were drained through a compromised DebugBear monitoring script. If your site loads a DebugBear script, remove it until the company says it is safe, then list every third-party script you load. Details and sources
  • Supabase changes a default today (30 October): new tables will not reach your app until you grant access. Check the tables your app uses and add explicit grants with row level security. Details and sources
  • GitLab fixed a maximum-severity flaw that needs no login. If you host GitLab yourself, update to the fixed version of your line today. Details and sources
  • Tailscale fixed SSH flaws that could reach root-only sockets. Update to 1.104.4 or newer on every server. Details and sources
  • OpenCode Console breach: if you saved AI provider keys there, revoke them on each provider's own dashboard, not just in Console. Details and sources

Plan this week

  • Binance says a hack cost about 6.3 billion dollars. Do not move funds in a hurry, turn on app-based two-factor sign-in and a withdrawal allow list, and ignore messages offering compensation. The final amount and the attacker are not confirmed. Details and sources
  • Telegram for Android flaw could run code when you answered a call: update to 12.10.4. Details and sources
  • Stolen Microsoft 365 sessions hit 79 organizations: check your registered MFA methods, devices and inbox rules. Details and sources
  • Two critical Wasmtime flaws can let a WebAssembly module escape its sandbox: update if you run code from outside parties. Details and sources
  • GMO in Japan shut down its Desktop Cloud after a breach that may reach 26,739 rented servers. If you kept passwords or trading keys on one, rotate them and check your accounts. The ransom and how they got in are not confirmed. Details and sources

Good to know

  • Ransomware affiliates ran intrusions with AI agents: patch and hide internet-facing remote-access tools, require MFA, keep one backup ransomware cannot reach. Details and sources
  • Update on PHP2Shell: CISA now lists the PHP flaws as exploited, so update PHP and check logs. Details and sources

New this week on the site

A free tool card for SkillSpector (check an AI skill before you install it) and an A to Z filter in the glossary.

Videos every Tuesday and Thursday at 20:00 (Madrid) on YouTube, urgent news as short videos on YouTube and Instagram: @safet2ship. Reply to the email with questions, and never send passwords, keys or customer data.

Get it in your inbox

One email a week, free. Unsubscribe any time.

Subscribe to the newsletter

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