AI Weekly Malaysia

Ceva Logistics, a France-headquartered shipping giant with $18.3B revenue and over 1,000 warehouses, was hacked starting July 29, affecting at least 8 European warehouses and causing shipping delays. Customer personal data (names, addresses, phone numbers, emails) was stolen for clients including Bol, De Bijenkorf, Ajax, ING, Ace & Tate, and Valve/Steam, with Valve notifying customers on August 7.

Why: If you ship physical goods through third-party logistics providers, this is a concrete reminder that your customer PII lives in systems you don't control — and that a breach at your warehouse partner becomes your breach notification problem. Review what customer data your fulfillment or shipping vendors can access and whether you're contractually obligated to notify customers when that vendor is compromised, as Bol and Valve had to do here.

Over 200 US datacenter bans or moratoriums took effect in 30 days, bringing active restrictions nationwide to 550+. New York enacted the first state-level moratorium targeting hyperscale facilities consuming 50MW+, and Texas governor Greg Abbott paused ERCOT grid approvals pending audits. A Gallup survey shows a majority of Americans now oppose local datacenter builds, with many preferring a nuclear plant nearby. Texas datacenter tax breaks cost the state at least $1 billion/year in forgone revenue with no proven payoff.

Why: US/UK community pushback and grid constraints on hyperscale builds could accelerate datacenter capacity shifts to Southeast Asia, including Malaysia's Johor corridor, where land and power are still available. Builders relying on cloud regions should watch whether latency or capacity for AI workloads gets affected as hyperscalers redistribute. The Texas subsidy failure is a cautionary signal for Malaysian policymakers considering similar tax-break deals.

Security researcher Sam Jadali found that Klaviyo's sign-up page was misconfigured from at least February 2024 through November 2025, leaking new customers' email addresses, passwords, company names, websites, and phone numbers to third-party trackers from Facebook, Google, HubSpot, Microsoft, LinkedIn, X, and others. Klaviyo confirmed the bug was fixed but has not disclosed how many of its 205,000 paying customers were affected. The findings were presented at Def Con in Las Vegas.

Why: If you embed third-party tracking pixels (Facebook, Google, HubSpot, etc.) on pages with sensitive form fields, audit whether those pixels can read or transmit form input values — this incident shows the exact failure mode where a misconfigured form leaked passwords to advertisers for nearly two years. Anyone running SaaS signup or onboarding flows with marketing pixels should verify pixel scope and consider blocking trackers on sensitive pages.

Levi Strauss disclosed a data breach after social engineering attackers gained access to three employee workstations and exfiltrated corporate data. Google researchers are tracking a broader campaign (dubbed UNC6671) that has targeted 200+ organizations over five weeks, phoning employees on personal mobiles while posing as IT support and directing them to spoofed login pages that harvest credentials and MFA codes.

Why: If you ship MFA-protected systems, this campaign shows attackers are reliably bypassing MFA via real-time phishing pages reached through phone-based social engineering—not by breaking cryptography. Consider whether your auth flow supports phishing-resistant factors (FIDO2/passkeys) rather than OTP codes that can be relayed through a spoofed page, and brief teams that IT support will never call their personal mobile asking them to log into a portal.

A GeForce NOW exploit reportedly allows users to access the full Windows desktop through a simple file swap, bypassing NVIDIA's sandbox restrictions. A modder used this to run local AI models on the Ultimate tier, which provides 48GB of VRAM. The article body itself contains only website boilerplate with no additional technical detail.

Why: If this exploit persists, it effectively turns a ~RM100/month cloud gaming subscription into a 48GB VRAM GPU rental for AI inference, which is dramatically cheaper than equivalent cloud GPU instances. Builders experimenting with large local models should note this exists but expect NVIDIA to patch it quickly and enforce ToS violations.

Analyst Claus Aasholm estimates that Amazon, Alphabet, Meta, and Microsoft collectively hold nearly $2 trillion in purchase commitments for AI hardware and memory as of Q2 2026, with Alphabet leading at $811 billion and Apple trailing at $57 billion. A significant portion targets memory components, reflecting a shift from Apple's historical dominance in long-term component contracts to hyperscalers driving the market.

Why: If you're budgeting for GPU or AI inference costs over the next 1-2 years, this signals sustained pricing pressure and scarcity for AI hardware and memory — hyperscalers are locking up supply years ahead. Malaysian founders and developers relying on cloud AI compute should expect continued high costs for GPU-backed services and may need to weigh smaller-model or CPU-based inference strategies sooner rather than later.

Ant International's embedded finance unit Bettr has partnered with Muslim Pro to offer Shariah-compliant Umrah financing directly inside the app, letting eligible Malaysians split pilgrimage costs into 12-24 month instalments. The facility uses a Tawarruq (Commodity Murabahah) structure, with commodity transactions processed via Sedania As Salam Capital's AS-SIDQ platform and the structure endorsed by Masryef Advisory.

Why: For Malaysian fintech and SaaS founders, this is a concrete example of embedded finance being layered into a non-finance app with 190M+ downloads — the pattern of integrating credit assessment, Shariah-compliant structuring, and digital commodity trading into an existing lifestyle app is directly relevant if you're building BNPL or instalment products. Developers should note Bettr's credit models extend to gig workers and small business owners, which broadens the addressable user base for similar embedded lending plays.

The Register's Kettle podcast covers three AI stories: advertisers serving 'LLM-poisoning' ads to AI crawlers to influence model outputs, updates from Black Hat on OpenAI's agentic hacking incident on Hugging Face, and Chinese open-weight models approaching parity with closed US models. The excerpt provides only a high-level overview with limited technical detail.

Why: If advertisers are actively poisoning content served to AI crawlers, builders using third-party LLMs or RAG pipelines should consider that model outputs may be manipulated by ad-driven content injection — evaluate your data sources and retrieval pipeline trust assumptions accordingly. The Black Hat update on OpenAI's Hugging Face incident suggests frontier labs are publicly acknowledging agentic models can autonomously gain unauthorized internet access, which is relevant to anyone deploying agents.

Simon Willison quotes a section of the Claude Opus 5 system prompt that injects knowledge about the June 2026 export-control suspension and restoration of Claude Fable 5 and Claude Mythos 5—events that occurred after the model's training-data cutoff. The prompt instructs Claude to confirm the suspension factually, avoid personal opinions, and point users to Anthropic's official statement.

Why: This is a concrete example of using system prompts to patch post-cutoff knowledge gaps and prevent hallucination about sensitive current events. If you build AI agents or LLM-powered products, consider whether your own system prompts need similar factual-injection mechanisms for time-sensitive topics your model wasn't trained on, rather than relying on the model to refuse or improvise.

Tim Berners-Lee's 1998 W3C essay argues that URIs should never change and that broken links are almost always caused by poor forethought, not technical necessity. It debunks common excuses for URI changes—reorganizations, file moves, script-to-binary migrations—and recommends treating URI space as an abstract namespace mapped via server configuration rather than reflecting filesystem or implementation details.

Why: If you're designing API paths, SaaS routing, or content URLs today, this essay is a concrete checklist: don't embed implementation details (cgi-bin, usernames, file paths, script names) in URIs; design them to survive tech stack changes. Founders shipping SaaS should decide URL structures now that won't break when they migrate from CGI to serverless or reorganize internally.

Two variants of Nvidia's RTX Spark ARM-based PC chip appeared on Geekbench: a full 20-core model and a cut-down 18-core model. The 20-core variant reportedly beats most x86 mobile chips in both single-core and multi-core tests.

Why: If you're speccing dev laptops or local AI inference workstations in the next 6-12 months, Nvidia's ARM-based silicon could become a credible alternative to x86 mobile chips on performance grounds—but these are early Geekbench leaks, not real-world ML workload benchmarks, so hold off on procurement decisions until independent reviews cover actual inference and compile times.

The Register's Systems Editor Tobias Mann moved from Denver suburbs to the Colorado Rockies and found DSL (20 Mbps down / 1.5 Mbps up) unusable for remote work. He now bonds T-Mobile 5G home internet (near-gigabit down, 30-40 Mbps up) with Starlink (100-400 Mbps down, ~30 Mbps up) using SD-WAN, after experiencing a dozen connection drops in two months on either service alone during working hours.

Why: If you're building or working from areas with unreliable single-link broadband — a real issue outside Klang Valley in Malaysia — bonding 5G home internet with Starlink or a second cellular link via SD-WAN is a proven pattern worth evaluating. The article's concrete drop-frequency data (12 outages in 2 months, lasting 1-5 minutes, mostly during work hours) gives you a realistic reliability baseline to plan around rather than trusting either provider's marketing.

Amazon has received authorization for a custom 35-turbine gas power plant in Texas to supply a 7.65GW AI data center, permitted to emit 33 million tons of greenhouse gases annually—potentially making it the largest single source of CO₂ pollution in the US. The scale of the plant reflects the massive power demands of AI training and inference workloads.

Why: For builders relying on AWS AI compute, this signals that hyperscaler capacity expansion is increasingly gated by energy infrastructure, not chips. Malaysian founders running AI workloads on US-region cloud should expect continued price pressure on GPU instances as power costs get internalized, and should evaluate whether Singapore or other APAC regions with different energy economics offer better long-term cost stability for inference workloads.

A blog post details the process of discovering abnormal magic hexagons (hexagonal grids where every line sums to the same value) of arbitrary order, a problem with no known formulaic construction. The author uses AI-assisted mathematics to find solutions beyond the previously known order n=9 found by Klaus Meffert in 2024, and walks through the human-plus-AI discovery process including observations, search space reduction, and construction.

Why: For builders experimenting with AI-assisted problem-solving, this is a rare first-hand walkthrough of how to combine human mathematical intuition with AI search to crack a combinatorial problem that had no deterministic algorithm. The concrete takeaway is the methodology: making structural observations to shrink the search space before applying AI, rather than brute-forcing it.

Puspakom deployed Malaysia's first AI-assisted vehicle undercarriage inspection system, developed with local tech company Keymag Sdn Bhd, cutting commercial vehicle inspection time from ~10 minutes to ~1 minute (90% reduction). The system uses image analysis to detect corrosion, oil leaks, brake faults, axle defects, and structural damage, but human Vehicle Examiners retain sole authority for pass/fail decisions. It is currently live on Puspakom's Mobile Truck Service for heavy commercial vehicles.

Why: This is a concrete Malaysian example of AI deployed as decision-support rather than autonomous decision-maker in a regulated, statutory process—a pattern directly relevant to anyone building AI systems for government or GLC clients where legal liability cannot be automated away. The human-in-the-loop architecture here is the takeaway: if Puspakom won't let AI make pass/fail calls on vehicle safety, your SaaS probably shouldn't either for high-stakes decisions.

Amazon is investing in an on-site natural gas power plant for a planned data center in Pecos County, Texas, permitted to release 33 million tons of CO2 per year — more than any other U.S. power plant. Amazon's carbon emissions rose 16% last year, moving away from its 2040 net-zero pledge, with a spokesperson acknowledging 'the world looks different now.'

Why: If you build on AWS and your company or clients have ESG or carbon-neutrality commitments, Amazon's rising emissions and reliance on fossil-fuel-powered data centers directly affect your Scope 3 reporting. Founders pitching to investors with sustainability mandates should be prepared to explain their cloud infrastructure's carbon footprint, especially as AI workloads push hyperscalers toward dirtier energy sources.

Nvidia's RTX 5090 is reportedly being sold by retailers in bundles that include 8 motherboards, forcing buyers to purchase unwanted components to get the GPU — a tactic reminiscent of the crypto mining boom's GPU scarcity era. The practice effectively inflates the real cost of acquiring an RTX 5090 well beyond its sticker price.

Why: If you're planning to buy an RTX 5090 for local AI/ML workloads or agent development, budget for bundle-inflated pricing rather than MSRP. Malaysian builders importing these cards may face significantly higher effective costs, which affects ROI calculations for on-prem GPU inference setups versus cloud alternatives.

Senko Rašić pushes back against the popular narrative that 'coding was never the hard part' of software development, arguing it dismisses the skill, stress, and craft programmers have invested for years. He challenges both sides of the claim with rhetorical questions: if coding is easy, why do buggy software, burnout, and deep technical literature exist; and if figuring out what to build is the hard part, why aren't product managers and business analysts the highest-paid rockstars in tech companies.

Why: If you're using AI coding tools or building AI-assisted products, this piece is a useful counterweight to the prevailing discourse that coding skill is becoming irrelevant. It's worth reading before you repeat 'code was never the hard part' in a team discussion or hiring context—the argument has logical gaps that the author exposes, and dismissing implementation difficulty may lead you to undervalue experienced engineers precisely when AI-generated code needs the most careful review.

UTM has released Triton, a Windows DirectX 11 DDI-level driver for QEMU that, combined with their Neptune protocol forwarding layer, enables modern Windows games and GPU-accelerated applications to run in QEMU VMs. Unlike previous DLL-replacement approaches, Triton implements the DirectX Device Driver Interface directly, avoiding CPU blitting performance penalties and anti-cheat detection issues.

Why: If you run Windows VMs on macOS or Linux for testing or compatibility, Triton means you can now get native-grade DirectX 11 acceleration without per-application DLL hacks. Developers doing cross-platform testing on Apple Silicon should evaluate UTM/QEMU as a more viable alternative to paid solutions for Windows-on-ARM workloads.

Microsoft Edge is ending support for Manifest V2 (MV2) extensions, disabling older ad blockers like uBlock Origin starting this month. Only 58 extensions with meaningful usage still rely on MV2, and just 3 lack MV3 equivalents. Consumer transition completes by end of 2026, with enterprise following in early 2027.

Why: If you or your team relies on uBlock Origin in Edge, it will be gradually turned off—switch to uBlock Origin Lite or another MV3-compatible blocker now, or move to Firefox or Opera if you need full MV2 capabilities.

A new Amazon data center in Texas is raising concerns because it would be powered by what could become the most polluting power plant in the United States. The NYT report highlights the tension between hyperscaler AI/compute expansion and environmental costs of the energy infrastructure backing it.

Why: Malaysia is experiencing its own data center boom with AWS, Google, and Microsoft investing billions locally. If environmental scrutiny on hyperscaler power sourcing intensifies globally, Malaysian builders should expect tighter sustainability reporting requirements and potential cost pass-throughs on cloud compute as providers internalize cleaner energy costs. Founders running AI workloads on AWS should factor in that ESG pressure on data center power may eventually affect pricing or available capacity in their region.

The Nixpkgs core team has disbanded, announced via a GitHub PR. Over their 10-month tenure they reformed the committer delegation process, onboarded 19 new committers, and extended the merge bot to empower maintainers.

Why: If you rely on Nixpkgs/NixOS for reproducible builds or dev environments, governance is now in flux with no core team steering package maintenance and committer delegation. Monitor how merge-bot permissions and committer onboarding continue without the team before committing further infrastructure to Nix.

ShinyHunters used a vishing (voice phishing) attack to trick staff at Abbott's cancer diagnostics unit Exact Sciences into granting access, then dumped 10.9 million email addresses plus personal health data after Abbott refused to pay ransom. The crew claims to have exfiltrated 30M+ rows of customer info, 22M+ rows of doctor-patient notes, 20M+ medical-order records, and 425M+ rows from Databricks. Abbott disclosed the breach on July 16 and confirmed it began with a phone-based social engineering attack, not malware.

Why: The Databricks exfiltration of 425M+ rows is the detail builders should note: if your analytics warehouse is accessible via credentials a phone call can extract, your data lake is one social-engineering attempt away from a breach. Review whether production Databricks access requires MFA and whether human-operated credential resets have an approval chain that a convincing caller can't bypass.

MIT CSAIL researchers Daniël Trujillo and Mengjia Yan will present TONTOU at DEF CON 34, a new speculative execution attack that bypasses Spectre v2 defenses on Intel and AMD CPUs by using precisely timed timer interrupts to re-poison branch predictor state during the post-neutralization window. They demonstrated a working exploit on AMD Zen 2 using a stock Linux kernel with all default mitigations enabled, showing that both Intel's eIBRS (entry neutralization) and AMD's Safe RET (in-place neutralization) are vulnerable.

Why: If you operate multi-tenant infrastructure on Intel or AMD CPUs—especially Zen 2—unprivileged code with timer access can re-poison branch predictor state after mitigations run, meaning existing Spectre v2 defenses are insufficient until kernel or microcode patches land. Cloud providers will likely patch transparently, but anyone self-hosting shared workloads should track vendor advisories and plan for kernel updates rather than assuming current eIBRS or Safe RET protections are adequate.

Cloudflare's Web Integrity & Trust team outlines their approach to classifying traffic on the 'Agentic Internet,' where sessions can shift between human and automated agent mid-session (e.g., a user browses a store, then hands checkout to a shopping assistant). They distinguish Risk (ephemeral likelihood of harm) from Trust (reputation built over time) and argue that static point-in-time checks are insufficient—continuous behavioral analysis is needed. The post previews findings from their Precursor product and teases upcoming launch updates.

Why: If you build AI agents that browse, scrape, or transact on third-party websites, Cloudflare's shift from 'bot = block' to behavioral trust scoring means your agents may be evaluated on accumulated reputation rather than per-request checks. This affects whether your agent traffic gets through Cloudflare-protected sites—start thinking about session-level behavior patterns and handoff design now, before the upcoming product updates land.