AI Weekly Malaysia

Summaries

Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.

Reset

Showing 1-12 of 12 results

DateProviderScoreSummary
17 Nov 2026, 7:00 AMHacker News8.0 Optimizely compromised, served malware on Zoom, GitLab

On 16 November 2026, attackers wrote their own code into the Project JavaScript field of Optimizely Web customer projects, so malicious JS was served from cdn.optimizely.com to visitors of 178 organisations including Zoom, GitLab, Salesforce, BBC, CNN, IKEA, HSBC, Equifax, Ledger and Peacock. The payload swapped crypto wallet addresses, skimmed card data, stole cookies and screenshots, and on iOS delivered the Coruna and DarkSword exploit kits, with verified crypto theft already on-chain. Three loader variants were seen — a plain script tag to https://1688360.cc/track.js and the same URL base64-encoded and decoded via atob() — and by 21:52 UTC the code was down to 1 of 188 infected snippets, from 169 at 20:56 UTC.

Why: The whole attack worked because the file stayed on cdn.optimizely.com with a valid certificate, so a CSP that allowlists Optimizely's CDN would not have blocked it — the payload arrived from a host you already trust. If you run Optimizely Web, go read the Project JavaScript field in each project dashboard directly rather than assuming your own code is clean, and treat integrity monitoring plus hash-pinned CSP as the control that would actually have caught this. Searching logs for '1688360.cc' misses the base64+atob variant, so detection needs to flag any newly injected script loader, not a known-bad domain.

17 Nov 2026, 3:53 AMTechCrunch7.5 Uber says hackers stole information on close to 150,000 driver’s licenses during data breach

Uber is notifying close to 150,000 drivers that their names, addresses, dates of birth, and driver’s license numbers were stolen in an October breach at Fireworks AI, a provider that gives developers access to open-weight AI models. Uber said its alerts for unauthorized access to its Fireworks environment did not trigger because the hackers used Fireworks’ own internal credentials. Notion and Cursor also confirmed data theft from the same Fireworks breach, which Fireworks attributed to a financially motivated group seeking to sell stolen tokens for accessing LLMs.

Why: If you send customer data or production credentials to a third-party AI provider, this shows your own monitoring may not fire when the provider’s internal credentials are compromised. Treat LLM access tokens and any PII shared with AI infrastructure vendors as high-value secrets: audit what you send, scope and rotate tokens, and ask vendors specifically how they detect misuse of their own internal credentials.

18 Nov 2026, 7:18 AMHacker News6.5 Microsoft's ONNX Runtime has disappeared from GitHub

The GitHub URL for microsoft/onnxruntime returned a 404 at the time of the post, and the linked page is just GitHub's generic error/navigation shell rather than a repository. The Hacker News submission drew 334 points and 72 comments (published 2026-11-17), but the captured text contains no Microsoft statement, redirect, or explanation for why the repo page is missing. Nothing in the source confirms whether this is a rename, a migration, a permissions change, or an outage.

Why: If onnxruntime is in your inference stack, treat this as a checkable unknown rather than a deprecation notice: confirm today that your pinned versions still install from PyPI/NuGet, that your lockfiles resolve, and that you have a mirror or vendored artifact path if the canonical repo stays unavailable. Teams that only pull from source builds or GitHub releases should verify their build pipeline still has a reachable source before the next deploy.

17 Nov 2026, 3:12 PMThe Hacker News6.0 Hijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits to CNN, BBC and Zoom Visitors

The Hacker News headline reports that hijacked Optimizely scripts served a card skimmer and iOS exploit kits to visitors of CNN, BBC and Zoom. The supplied text contains only the headline plus site navigation — no compromise window, affected script versions, traffic numbers, or vendor response are included, so the mechanism cannot be described from this source.

Why: The concrete takeaway is the attack shape, not the details: a third-party experimentation/marketing script — the kind embedded site-wide — was the delivery vehicle for payment-card skimming on major publishers. If you load any vendor tag on a page where card data is entered, your own code review will not catch this; decide now whether that tag needs to run on checkout pages at all, and whether your CSP allows it to pull further scripts. We cannot say from this text which Optimizely customers or which dates were affected.

18 Nov 2026, 2:45 PMThe Hacker News5.0 Attackers Compromise Microsoft's Agent Framework PyPI Package to Steal Cloud Credentials

The Hacker News headline reports that attackers compromised the PyPI package for Microsoft's Agent Framework in order to steal cloud credentials. The excerpt supplied here is truncated — it contains only the headline, publication date (18 Nov 2026) and site boilerplate, with no package name, affected versions, compromise mechanism, discovery timeline, or indicators of compromise. Treat the claim as unverified detail-wise until the full write-up is read.

Why: The concrete decision this forces: any AI agent code you ship pulls cloud credentials, so a poisoned dependency in an agent framework is a direct path to your AWS/GCP/Azure keys. Since this excerpt gives no version range or IOC, you cannot check exposure from it — go read the full post before deciding whether to pin, rotate keys, or swap frameworks. Do not treat 'Microsoft publishes it' as a trust signal for the PyPI artifact itself.

18 Nov 2026, 6:32 AMArs Technica5.0 Hundreds of websites deliver potent malware cocktail to unsuspecting visitors

Ars Technica reports that malicious code delivered through Optimizely — a third-party script many sites embed for A/B testing and personalization — reached visitors on hundreds of websites, pushing what the piece calls a "malware cocktail" that includes cryptocurrency-theft payloads and iOS exploits. The available text is truncated after the opening section, so the specific compromised domain count, the timeline of the Optimizely compromise, the named malware families, and any vendor response are not present in what we have. The only community signal given is a 6-comment thread on the story.

Why: The one decision-relevant fact here is the delivery vector, not the malware: the payload arrived through a third-party script tag rather than the sites' own code, so anyone whose pages load Optimizely or similar tag-manager/analytics snippets inherited the exposure without changing a line of their own repo. Before the meet, pull your list of third-party scripts and check which ones you cannot remove or self-host — that list is the actual blast radius. Because the article text is cut off, we cannot say from this source which Optimizely customers or regions were hit, when it started, or whether it is resolved, so don't plan remediation specifics off this item alone.

17 Nov 2026, 6:12 AMTechCrunch4.5 Cyber giant Infoblox confirms security incident after hackers access ‘company information’

On November 16, 2026, Infoblox confirmed a security incident in which hackers accessed "certain company information" through a compromised third-party data migration vendor; TechCrunch reports the vendor provided SharePoint data migration services, and one person with knowledge of the incident said sensitive customer data was taken. Infoblox says it activated incident response, contained the incident, and has "no indication" its products, cloud services, software updates, or build-and-release processes were involved, but it would not say how many customers were affected. One source said Infoblox has terminated work with the vendor, which the company did not confirm and has not named.

Why: The entry point was a data migration vendor with access to SharePoint — the same category of read-and-export access that contractors, BI tools, and migration scripts get in most Microsoft 365 tenants. If you've ever handed a vendor tenant-wide SharePoint or Graph permissions for a one-off migration, this is the concrete case for scoping that access to specific site collections, time-boxing it, and revoking it after cutover — and for checking whether your SSO provider still grants live sessions to vendors you no longer work with.

18 Nov 2026, 8:00 PMTom's Hardware4.0 SSDs, laptops, and phones may get cheaper as consumer NAND spot pricing drops 20%

Tom's Hardware reports that consumer NAND spot pricing has fallen 20%, with Bank of America expecting contract prices to follow, citing oversupply in the consumer market, declining demand, and growing Chinese competition. Beyond the headline claim and the 20% spot-price figure, the supplied page text is almost entirely site navigation and subscription boilerplate, so there are no retail prices, product names, or dates attached to the forecast.

Why: Spot price is what traders pay for loose NAND chips; contract price is what laptop, phone, and SSD makers pay — and the article only says BofA *expects* contract prices to drop, with no timeline or magnitude for retail. So the practical read for anyone speccing a dev laptop or NAS build is that a 20% spot move is not yet a 20% discount at the checkout, and there is nothing here concrete enough to schedule a purchase around. Wait for retail SKU pricing to actually move before treating this as a buying signal.

16 Nov 2026, 2:53 PMThe Hacker News3.0 BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server

The Hacker News headline reports that a group tracked as "BO Team" exploited Log4Shell (the long-patched 2021 JNDI flaw in Log4j) inside VMware vCenter to compromise a Russian company's code-signing server. The supplied page text is almost entirely site navigation and boilerplate — it contains no CVE identifier, affected vCenter version, intrusion timeline, victim name, or detail on what was signed with the stolen keys.

Why: The one actionable signal is that Log4Shell — a flaw with fixes available since late 2021 — is still being used as an entry point into vCenter, which means management-plane appliances are the unpatched gap. If you run vCenter, check its build/patch level this week, and check whether your code-signing keys or build pipeline are reachable from the same network segment as your hypervisor management interfaces. Beyond that, this excerpt gives you nothing to act on: no versions, no indicators, no victim detail.

18 Nov 2026, 7:00 PMTechCrunch2.5 China dominates battery graphite, but this startup could break the monopoly

Molten Industries has started a demonstration plant in Oakland that will produce about 300 metric tons of graphite annually, enough for 300 MWh of batteries or roughly 4,300 EVs. The startup says its methane-splitting process, using resistive heating likened to a 'massive toaster,' uses three times less electricity than existing methods. CTO Caleb Boyd says the plant's graphite is at cost parity with China plus tariffs, and future plants should match China's cost without tariffs.

Why: For most software, AI, and SaaS builders this changes nothing in their stack. The concrete takeaway is supply-chain risk: the article cites Chinese control of about 75% of the graphite anode supply chain and 97% of synthetic graphite anode production, while Molten's alternative is only a 300 t/yr demo plant whose parity depends on tariffs—so non-China anode supply is still policy-sensitive and unproven at scale.

17 Nov 2026, 8:25 PMThe Hacker News2.5 Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap

This item is only a headline and page shell from The Hacker News: 'Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap.' No body text, vendor name, researcher name, attack detail, affected versions, dates, or webinar schedule is included in the supplied excerpt. It is a webinar promotion, not a technical write-up or incident report.

Why: There is not enough here to act on. The headline implies GitHub SHA pinning, a common supply-chain control for locking dependencies to a specific commit, can be bypassed — but the text gives no mechanism, no affected tooling, and no remediation steps beyond registering for a webinar. Anyone relying on SHA pinning for CI dependencies should treat this as an unverified claim until the actual technical detail is published, and should not change workflows based on the headline alone.

18 Nov 2026, 10:00 PMTom's Hardware2.0 Global OLED monitor shipments doubled year-over-year in Q3 2026

Tom's Hardware reports that global OLED monitor shipments doubled year-over-year in Q3 2026, framing it as gamers upgrading displays as the technology gets cheaper. The headline also attributes component price pressure to AI demand. Beyond the doubling figure and the Q3 2026 timeframe, the supplied text is almost entirely site navigation and membership boilerplate — no shipment unit counts, vendor breakdowns, panel pricing, or component-cost data.

Why: There is not enough in this text to act on. The only concrete claim is a 2x year-over-year shipment figure for OLED monitors in Q3 2026; there are no prices, model names, panel suppliers, or quantified component-cost impact, so nobody should revise a hardware budget or procurement plan from this. If you need display purchasing signals, wait for the underlying shipment report rather than this headline.

Top