Urgent.News

What's breaking now, across thousands of outlets.

Tech

Cheapskates wouldn't pay for security help, got hit by ransomware, and went bust months later

The owner knew a guy...

Cheapskates wouldn't pay for security help, got hit by ransomware, and went bust months later

Two cases of security breaches highlight the importance of proper cybersecurity measures for small businesses. A construction firm initially refused security help due to budget constraints, only to suffer a ransomware attack and go out of business within months. The company had an unpatched Windows server with critical data on a shared backup drive, which became encrypted by the ransomware, leaving the business unable to pay employees or access vital information.

In a second case, a phishing attack was launched via a fake Microsoft 365 login page, tricking an executive's email account into revealing login credentials. This allowed the attackers to access the second company's Microsoft 365 account, potentially compromising sensitive customer data, bank accounts, and enabling further fraudulent activities.

The victim's company detected the suspicious login through TarBot, an app designed to identify anomalous logins, and successfully thwarted the attack. The incident underscores the effectiveness of phishing-resistant MFA methods, such as hardware keys or passkeys, in preventing sophisticated phishing attacks.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at theregister.com →

More in Tech

Migration Diary: Port the Tool Contract Before a Free Server Inherits Paid Endpoints

You should port the tool contract before you repoint a coding workflow at free model access. Leftover paid endpoints, unbounded retries, and vendor tool names survive cancellation and keep steering…

  • Port the tool contract before switching to a free server.
  • Create a portable contract and leftover scan for rehearsal.
  • Use a decision table to classify bindings for migration.

One build, every environment: runtime configuration for micro frontends

Look at your pipeline. If it builds staging and production separately from the same commit, you are shipping an artifact nobody tested. You tested the staging one.

  • Implement runtime configuration to avoid separate builds for each environment in micro frontends.
  • Application fetches environment-specific values as a small JSON document at startup.
  • This approach reduces build waste, potential failures, and enables quick rollbacks.

More from Thursday 8 October →