Urgent.News

What's breaking now, across thousands of outlets.

Tech

Cheap deal, costly click: Singapore loses S$1.4m to social media phishing scams since July 2026

SINGAPORE, Oct 3 — With about 87 per cent of people in Singapore aged 15 and above accessing top social media site...

Cheap deal, costly click: Singapore loses S$1.4m to social media phishing scams since July 2026

SINGAPORE — Since July 2026, at least 246 phishing scams have been reported on popular social media platforms like Facebook, Instagram, and TikTok, resulting in losses exceeding S$1.4 million, according to police reports. These scams typically involve ads for discounted household items, food, or fashion, directing users to fraudulent websites where they are asked to input personal banking information.

Some victims even divulge one-time passwords or authorization tokens, making them unaware of the theft until unauthorized transactions appear. To protect themselves, individuals are advised to enable security measures such as transaction limits, two-factor authentication, and the money lock function on their internet banking. No personal data, banking details, or one-time passwords should ever be shared with anyone. Should doubt arise, Singaporeans can contact the 24/7 ScamShield helpline at 1799 for assistance.

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

Read the original at malaymail.com →

More in Tech

Express Node.js Structured Logs — Poll Error Search for 30-Day Cost Attribution

Short answer: have the Express Node.js service send structured logs for every completed AI-agent step, then poll the log search for new error events and trigger deduplicated Slack notifications.

  • Express Node.js service structured logs for each step completion
  • Differentiate event classes: attribution, diagnostic, and alert-delivery records

What OMA returns when its test gate fails

oh-my-agent (OMA) can rerun a configured test script when an active workflow tries to stop. This example exercises that behavior with manual hook calls and a deliberately broken expiry check.

  • OMA returns decision block when test gate fails
  • Failure reason: stop gate test failed
  • Issue resolved by fixing code comparison

Why a missing JavaScript file can stay missing after you deploy it

I built cachewhy around a small but costly HTTP cache mistake. Imagine a request for /missing.js that returns 404 with Cache-Control: public, max-age=2678400 . That lifetime is 31 days. A browser may reuse the missing response even after the file is deployed.

  • Missing JavaScript file persists due to long-lived HTTP cache.
  • Browser stores 404 response in private and shared caches.
  • Cachewhy tool reveals cache details and caching behavior.

More from Saturday 3 October →