vgws

👋 WELCOME to Phish & Tell™️, from Security Done Easy™️

You’re not just building a business.
You’re building something worth protecting.

🎣 TOP CYBERSECURITY NEWS STORIES OF THE WEEK

We know running a business, juggling family, and managing everything else can feel like spinning plates. The last thing you need is another security headache. That’s why Phish & Tell scouts trusted sources (The Hacker News, BleepingComputer, Dark Reading, Krebs on Security, and others) to bring you plain‑English explanations of the biggest cyber‑security stories affecting small businesses. Each short entry covers what happened, why it matters, and what you can do—so you can keep your business safe without getting lost in tech jargon.

  1. Newsletter platform Substack discloses data breach

    What happened: Substack, the platform many small businesses use for newsletters, revealed that attackers breached its database in October 2025. The stolen information includes email addresses, phone numbers and internal metadata; fortunately, credit‑card details and passwords were not accessed. Substack patched the vulnerability and notified users.

    Why it matters: If you publish a newsletter or subscribe to one, attackers could use your stolen contact information to send convincing phishing messages or scam calls. Because small businesses often build customer relationships through newsletters, a breach of this platform can put your clients’ trust at risk.

    What you can do: Treat emails and texts that appear to come from Substack with caution—especially if they ask you to click links or provide payment info. Remind your subscribers to ignore unsolicited messages and always access your newsletter through the official Substack website or a known link.

  2. Critical n8n automation flaws allow remote code execution

    What happened: Security researchers uncovered multiple critical vulnerabilities in n8n, a popular open‑source workflow automation tool. Any authenticated user could run arbitrary system commands on the host server. The flaw could also expose stored credentials and secrets, allowing attackers to pivot to cloud services. n8n patched the issue in versions 1.123.17 and 2.5.2 and recommends users rotate their encryption keys.

    Why it matters: Many small businesses use n8n to automate tasks across apps like Slack, Shopify or QuickBooks. A compromised server could leak API keys and customer data, or let attackers hijack your automations. Because exploitation only requires a user account, disgruntled employees or compromised logins pose a real risk.

    What you can do: Update to the latest n8n release and rotate your N8N_ENCRYPTION_KEY and other stored credentials. Limit who can create or edit workflows, and restrict the server’s operating system and network privileges. If updating immediately isn’t possible, follow n8n’s temporary mitigation guidance and monitor logs for unusual workflow changes.

  3. AI‑assisted attack compromises AWS environment in 8 minutes

    What happened: Researchers at Sysdig detailed an attack where criminals used credentials left in public AWS S3 buckets and leveraged large language models (LLMs) to automate reconnaissance and code generation. Within eight minutes they moved across multiple accounts and even hijacked GPUs for their own AI training.

    Why it matters: Storing access keys in publicly accessible cloud storage is a common mistake for small teams. Coupled with AI‑powered automation, attackers can now move faster than traditional defenses. A breach like this could lead to stolen data, misuse of your computing resources, and inflated cloud bills.

    What you can do: Never store AWS access keys in repositories or buckets. Periodically check to make sure they haven’t been left there accidentally. Use temporary IAM roles and rotate credentials regularly. Implement least‑privilege policies and monitor logs for unusual activity. Consider enabling runtime detection tools that can spot lateral movement and unusual resource provisioning.

    Not sure what applies to your business or what your options are? Let’s talk.

🔍 In Case You Missed It (ICYMI)

🙋‍♀️ Top Reader Questions of the Week

Below are five questions from small‑business owners over the past week. What questions do you have?

  1. What should be in our incident response plan?

    • Define clear procedures for identifying potential security incidents and how employees should report them.

    • Outline the responsibilities of team members, including IT, management, legal, and communications staff.

    • Detail how you will communicate during an incident—internally with staff and externally with customers, partners, and the public—and include contact info for cyber insurance, legal counsel, and law enforcement.

    • Establish steps for isolating affected systems or networks to prevent further damage and protect unaffected areas.

    • Specify how to preserve logs and other evidence, identify the root cause, and determine the extent of the breach.

    • Explain how to restore operations, including rebuilding systems from clean backups and verifying systems are secure before going back online.

    • Include a process for reviewing what happened, documenting lessons learned, and updating policies and training accordingly.

    • Keep the plan concise (1–2 pages). You can use free templates from CISA or NIST as a starting point, or hire a consultant to help, which runs a few thousand dollars.

  2. What’s the minimum we need to spend on cybersecurity?

    • Focus spending on core defenses first: deploy multi‑factor authentication (MFA) and a password manager (often free or under $500); invest in off‑site backups and disaster recovery ($1K–$5K); provide regular employee training ($500–$2K); obtain a cyber‑insurance policy ($1K–$3K); and ensure each device has reputable endpoint protection ($500–$2K).

    • Avoid costly “advanced” tools until you’ve mastered the basics—many security incidents are prevented by good passwords, MFA, patching, and user awareness. You can also use a managed security service provider to manage security for you until you grow enough to hire your own security team.

    • Take advantage of free or low‑cost options (e.g., Bitwarden, built‑in cloud security), and remember the return on investment: every dollar spent on prevention can save six or more dollars in breach recovery.

  3. How much will a ransomware attack cost my small business?

    • Consider total costs: beyond ransom demands (which can range up to $500K), factor in recovery and restoration expenses, downtime, lost productivity, regulatory penalties, legal fees, and credit monitoring.

    • Average recovery costs for small businesses fall between roughly $25K and $115K+, depending on industry and preparedness.

    • Paying a ransom funds criminal activity and doesn’t guarantee data recovery; most experts advise against it.

    • The cost of prevention is typically much lower—around one‑tenth the price of dealing with a successful breach.

  4. Should we get cyber insurance? What does it cover?

    • Cyber insurance is increasingly vital for small businesses because it covers key breach‑related expenses: notifying affected customers, providing credit monitoring, paying for forensic investigations, covering legal and regulatory defense, recouping lost revenue from business interruption, and reimbursing ransomware recovery costs (though not the ransom itself).

    • Premiums for small businesses typically range from about $1K–$3K per year.

    • Basic security controls are usually required to qualify: insurers expect MFA, protected backups, employee awareness training, and up‑to‑date endpoint protection.

    • Coverage terms and exclusions vary widely, so shop around, compare policies carefully, and choose a plan that fits your risk profile and industry.

  5. What’s a disaster recovery plan and do we need one?

    • Identify how quickly you need to restore operations and how much data loss you can tolerate.

    • Detail backup and restore procedures (see my blog article for details).

    • Plan for alternative work arrangements so employees can continue serving customers if your main site goes down.

    • Specify how you’ll notify staff, customers, and partners during a disruption, and assign a point person to coordinate updates.

    • Test your plan at least quarterly to ensure backups actually restore and staff know their roles.

    • For small businesses, a simple plan is often enough: list your critical systems, backup schedules, and recovery steps in 1–2 pages

    • Disaster recovery plans are essential even for small operations—a day of downtime can cost thousands—yet developing a basic plan can be inexpensive (often under $2K) and offers peace of mind.

🤖 The LOL-gorithm

🧷 THE SAFETY SNAP

Online Deepfake Abuse and “Nudification” Tools

What’s happening: A Guardian investigation found at least 150 channels on Telegram dedicated to creating and sharing non‑consensual “nudified” images of women. Users upload photos of any woman and AI tools generate nude or sexualised images; some channels distribute these images for free, while others charge a fee. The anonymity and encryption of such platforms make it difficult to trace perpetrators, and moderators often look the other way. Law enforcement and human‑rights groups warn that the spread of these AI‑powered deepfakes is fuelling a global wave of digital abuse.

Why it matters: Anyone can become a victim. Victims report severe mental‑health impacts, reputational damage, job loss and social isolation. Once a deepfake circulates, it is nearly impossible to retract, and small‑business owners who use personal branding or share images online could have their photos weaponized.

What to do:

  • Protect your brand: Use professional headshots with watermarks or brand logos and avoid sending private photos to people you don’t know well.

  • Monitor your digital footprint: Regularly search for your name and images online; if you find a deepfake, document it and report it to the platform and, if necessary, law enforcement.

  • Educate your team: Talk with employees about deepfake risks and encourage them to safeguard their photos.

  • Advocate for stronger laws: Support organizations pushing for legal protections against non‑consensual deepfakes and report abuse when you see it.

👂 TELL ME

P.S. Hit reply if you have questions or feedback — I love hearing from you!

You’re subscribed to Phish & Tell™️ because your business is worth protecting.

🩷

Keep Reading