AI Weekly Malaysia

The Hacker News rounds up six browser-based attack techniques it says security teams should track in 2026, citing Push data and Microsoft's Digital Defense Report. It claims reverse-proxy adversary-in-the-middle phishing kits (Tycoon2FA, Sneaky2FA, Evilginx) relay live credentials and session tokens to bypass most MFA, that roughly 1 in 2 phishing attacks now arrives outside email, and that 89% of phishing domains live under two days. It says ClickFix copy-and-paste attacks hit 47% of observed attacks per Microsoft and 52% of Push's Q2 2026 detections, with four in five ClickFix payloads reached from search engines, and describes an 'InstallFix' variant using malvertised fake install pages for developer tools including Claude Code and NotebookLM where the install command is swapped out.

Why: The concrete action item is the install-command path: if your README, onboarding doc, or YouTube tutorial tells someone to copy a curl/install command, an attacker can rank a fake page above yours and swap that command — and this piece names Claude Code and NotebookLM as already-targeted examples, meaning AI coding tools are now the lure. Second, if your product's MFA is TOTP or push, session-token relay means a phished session can survive login, so passkeys or other origin-bound auth is the thing to evaluate rather than adding another prompt. Note there is no Malaysia-specific detail in the text, so treat this as generic team hygiene, not a local incident.

OX Security researchers identified 101 npm packages that abuse the open-source 'Baileys' WhatsApp library to silently add victims' WhatsApp accounts to attacker-controlled groups and channels, a campaign dubbed PhantomSub. The packages have been downloaded 490,000 times in total, with 116,000 of those downloads in the last 30 days, and split into three variants: 19 fetch channel IDs from GitHub at runtime, 60 hardcode them in cleartext, and 14 embed them encoded/obfuscated. The write-up follows earlier August 2026 SafeDep findings on malicious Baileys forks and a September Xygeni disclosure about '@dappaoffc/baileys-mod'; one of the groups is assessed to be based in Indonesia and advertises mobile-game and app accounts including Mobile Legends: Bang Bang and TikTok.

Why: If you build or self-host a WhatsApp bot, the practical risk is not just a bad dependency: an already-authenticated Baileys session can be made to follow or join channels, and SafeDep's earlier finding also showed ad URLs being injected into every image and video the bot sends. Check your lockfile for any Baileys fork under a random scope or a name like 'ourin-baileys', 'noxleyss', or '@nexustechpro/baileys', and if one is present, remove it, rotate/re-link the WhatsApp session, and re-audit anything the bot posted. The 116,000 downloads in the last 30 days means these packages are still live and being pulled now, so this is a today check, not a backlog item.

Micron says RAM shortages will keep tightening through 2028, according to Tom's Hardware's report, and the company posted a record 86.25% gross margin alongside a headline figure of over $53 billion in quarterly profit. The accessible article text is mostly subscription and navigation boilerplate, so no unit volumes, pricing, contract terms, capacity numbers, or customer quotes are available to verify the figures or the shortage claim.

Why: If memory supply really stays tight into 2028, DRAM-heavy plans get more expensive: budget for higher RAM costs in new laptops, servers, and GPU boxes, and re-check whether self-hosting models or large in-memory workloads still beat paying per-token API or managed-database pricing. The 86.25% gross margin claim is the tell — that level of margin on memory implies buyers, not suppliers, absorb the shortage, so lock in quotes and contract lengths now rather than assuming 2027 prices. Note that the $53 billion quarterly profit figure comes from the headline only and the body text isn't readable here, so verify it before quoting it.

Anthropic introduced mods for Claude Code: small TypeScript functions that hook into events Claude Code emits (tool calls, permission prompts, UI draws) to run before, after, instead of, or wrapping them. A mod can rewrite prompts before they reach the model, block/retry tool calls, approve or deny permissions, redact secrets from tool output, and add or replace UI elements in the CLI, desktop app, or both. Mods ship inside plugins and are explicitly not sandboxed — they run with the same machine access as Claude Code itself, so the post says to install only from trusted sources.

Why: If your team runs Claude Code, this is a new install surface: mods arrive as plugins and execute unsandboxed with the same access as Claude Code, so the practical decision is whether to allow third-party mods at all and who reviews them. The useful capability to note is prompt/tool-call interception — you can now redact secrets from tool output before Claude reads it, or block and retry specific tool calls, without waiting on Anthropic to ship a feature. Hooks previously could not rewrite events, draw UI, or replace features; mods can, which changes what you'd build in-house versus install.

Federal prosecutors say a California tech CEO has been arrested and faces up to 20 years in prison over the alleged smuggling of roughly $300 million worth of Nvidia AI servers to China, with the hardware routed through Malaysia and Singapore using false paperwork. The excerpt (largely paywalled Tom's Hardware page) does not name the CEO, the company, the specific Nvidia server models, or the charges' filing details beyond the routing allegation and the maximum sentence.

Why: Malaysia and Singapore are named as the transshipment route, so anyone here sourcing Nvidia servers or renting regional GPU capacity should expect the paperwork question to get sharper: customs declarations, end-user certificates, and counterparty identity checks on who actually receives the hardware. If you are buying GPU boxes or cheap local H100/H200-class capacity through a reseller, this is the concrete risk case for asking where the units came from and who the end user is — an unverifiable supply chain is now a legal exposure story, not just a price advantage.

Micron's fiscal Q4 2026 beat consensus with adjusted EPS of $33.42 versus $31.61 expected and revenue of $54.23 billion versus $51.07 billion expected, up from $11.32 billion a year earlier. Guidance for the next quarter is also above expectations: roughly $61.5 billion in revenue and $38.15 adjusted EPS, against analyst estimates of $57 billion and $35.40. CNBC attributes the run — Micron stock is up more than 500% over the past year — to a worldwide memory supply crunch driven by AI demand, which the article says has spiked memory costs and raised prices for consumer electronics.

Why: Memory is a direct input cost for AI builders, and this report confirms the shortage is still getting worse rather than easing: guidance of $61.5 billion next quarter is up again from $54.23 billion, and the article explicitly links the crunch to higher consumer electronics prices. If you are planning GPU/cloud capacity, a hardware refresh, or per-token inference pricing for the next two quarters, budget for memory-driven cost inflation rather than assuming last year's rates hold.

Tom's Hardware reports Raspberry Pi prices are rising by up to 23%, the third price hike of the year, attributed to escalating LPDDR4 and LPDDR5 memory costs and broader component shortages. The published excerpt contains almost no product-level detail — no per-model pricing, no effective date, and no confirmation of which SKUs are affected beyond the headline figure.

Why: If you are speccing Pi-based edge nodes, kiosks, sensor gateways, or classroom kits, re-run your bill of materials against a worst-case 23% uplift rather than your old quote, and decide now whether to buy ahead of the next increase. Because the article gives no per-model breakdown, do not assume the 23% applies to the SKU you actually order — check pricing at your supplier before committing to a fixed-price build.

Ars Technica published a piece on 2026-10-01 headlined "Memory executives expect RAM shortage to continue through 2028," with a URL slug attributing the claim to Micron's CEO ("memory supplies are only getting tighter"). The article body as retrieved contains only Condé Nast cookie-consent and privacy-preference text — no quotes, no figures, no supply numbers, no named memory products or pricing are present in the source. Everything beyond the headline and slug is unsupported by the text provided.

Why: Only one actionable signal survives here: the claim that memory supply tightness is expected to run through 2028, attributed in the URL to Micron's CEO. If you are sizing a build now — workstations for local model inference, GPU nodes, or a server refresh — the decision to make is whether to buy capacity this cycle or commit to rented/API inference, because the article gives you no pricing, no capacity figures, and no timeline detail to model either option. Treat the headline as a reason to check current RAM and cloud instance pricing yourself before budgeting, not as a forecast you can quote to a finance team.

Microsoft published a technical analysis of NeedyMantis, a malware family used to keep long-term access in networks that were already breached, seen in a small number of targeted intrusions at telecommunications organizations, universities, medical nonprofits, intergovernmental organizations, and government contractors, with use dating back to at least October 2025. Microsoft found it while following indicators from Kaspersky's investigation into the DAEMON Tools supply chain attack, where signed DAEMON Tools Lite installers carried malicious code from April 8, 2026 until the developer replaced them with a clean version on May 5; Microsoft tracks that activity as Storm-3069. NeedyMantis arrives via DLL sideloading — a legitimate program plus a malicious DLL named after a file that program loads, plus an encrypted archive of the same name — using hosts including Poedit, curl, Vim, and TightVNC, and posing as DLLs from Microsoft Office, Broadcom, Intel, and NVIDIA, then connecting to C2 over HTTPS and switching to WebSocket.

Why: If you ship or depend on signed Windows desktop installers, the concrete lesson is the April 8 to May 5, 2026 DAEMON Tools Lite window and the sideloading pattern: a trusted exe (Poedit, curl, Vim, TightVNC) sitting next to a same-named malicious DLL. Microsoft published file hashes, domains, file paths, and hunting queries, so the actionable step is to run those indicators rather than assume your EDR caught it — and to stop placing third-party binaries in writable directories beside signed executables you ship.

The Hacker News' Sep 28 weekly recap leads with Bitget resuming Bitcoin withdrawals in phases after suspected North Korean hackers stole over $387M from hot wallets (Circle and Tether froze $339,100 in linked stablecoins), and Citrix patches for CVE-2026-88771 (unauthenticated arbitrary command execution via improper input validation) and CVE-2026-88772 (RCE/DoS), both under active exploitation, with CISA urging federal agencies to patch by Wednesday. It also flags a placeholder domain that appeared in roughly 1,700 repositories before someone registered it and served malicious lures, plus a PamStealer update adding live C2 payload decryption. The headline mentions AI agents going off-script, but the excerpt provides no detail on that item.

Why: The 1,700-repo placeholder domain is the only item here that touches ordinary builders: any copied sample code still pointing at an example domain is live attack surface someone can buy and weaponise, so it is worth grepping your repos and lockfiles for placeholder hosts you don't control. The Citrix CVEs only require action if you actually run NetScaler ADC/Gateway exposed to the internet — then patch now. The crypto hack and PamStealer are context, not decisions, and the text supports no Malaysia-specific impact.

Tom's Hardware reports that Nvidia's 7-year-old Shield TV Pro streaming box has received a roughly 50% price increase, and that Nvidia has discontinued the entry-level Shield TV, attributing both moves to soaring component prices amid an AI-driven memory shortage. The piece (published 2026-10-03) offers no actual price figures, memory contract data, or timeline — the visible text is almost entirely site navigation, membership prompts, and newsletter boilerplate.

Why: The only actionable takeaway is a direction of travel, not a number: an aging, low-volume consumer device from a major chip vendor is being repriced upward and its cheap tier killed, with AI memory demand given as the cause. Without the article's actual prices or any DRAM/NAND contract data, you cannot yet adjust hardware budget assumptions for GPUs, RAM, or edge devices — treat this as a signal to watch memory pricing before locking in 2026 hardware purchases, not as evidence to act on today.

Tom's Hardware reports that Micro Center is requiring photo ID and a signed declaration from customers purchasing an RTX 5090. The declaration reportedly has the buyer disclose where the GPU will be installed and pledge that the card will remain in the United States. The article body supplied here is almost entirely site navigation and subscription boilerplate, so no additional specifics — store locations, effective dates, pricing, or how the pledge is enforced — are available.

Why: If you source high-end GPUs through US retail for builds or resale into Malaysia, this is a change in the purchase process itself: photo ID plus a signed document tying the card to a disclosed install location. That paperwork is a paper trail, and it makes US retail sourcing harder to do quietly or at volume — plan on local or authorized-region channels instead. Note the text here gives no pricing, no date, and no enforcement detail, so treat any claim about how strictly this is applied as unverified until the full article is read.

Bitget confirmed that the $387.5 million drained from its hot and warm wallets on September 24, 2026 was enabled by a zero-day in unnamed third-party security products, per a SlowMist investigation. Attackers used the flaw to read a database password from an environment variable, run hidden scripts on at least three nodes starting August 31, 2026, obtain high-level internal credentials, and issue withdrawal commands that bypassed existing risk controls. Funds were taken across 11 blockchains and 13 assets, and only about $632,700 was frozen by Circle, Tether, and NEAR Intents.

Why: If you or a Malaysian client keep operating funds on a centralized exchange or rely on crypto rails for payouts, the concrete number here is the recovery rate: roughly $632,700 frozen against $387.5 million taken, under 0.2%. The breach did not come from Bitget's own code — it came from a third-party security product that had database credentials reachable as an environment variable — so the decision that changes is how you vet and segment vendors that sit inside your credential path, and how much you leave in hot wallets versus cold.

Tom Wojcik's essay traces one cause — the Strait of Hormuz, which Iran has kept closed since March using drones, missiles, mines and small boats — into fuel, food and winter heating costs, noting tanker traffic through it fell by more than 90% and that the IEA calls it the largest oil supply disruption the market has ever seen. Brent went from near $97 in early September to around $105 mid-month and $108 on 24 September, after Washington rejected Iran's 22 September written road map for a 60-day regional ceasefire and phased reopening of the strait. He also flags the Breakwave Tanker Shipping ETF rising more than 600% in the war's first two months and up over 2,300% for the year by early September, with supertanker day rates going from under $100,000 pre-war to a record of about $860,000 on 10 September.

Why: This is macro context, not a change to any tool you use — nothing in it tells a developer or founder to alter their stack. The only usable numbers are cost inputs: if your budget includes physical shipping, hardware freight or energy-linked pass-through, ~$860,000/day supertanker rates and ~$108 Brent are what reprice first. The piece contains no Malaysia- or Southeast Asia-specific data, so any local impact is something you would have to verify yourself rather than take from this essay.

Boston-based Atomic raised a $12.5M Series A led by Klass Capital and Madrona Venture Group, bringing total funding to just over $15M. Atomic simulates supply-chain scenarios and then recommends or automatically picks inventory levels and locations, and its ARR has quintupled since the start of 2026, with named customers DoorDash and HelloFresh. The company was incubated at DVx Ventures, has added longtime Tesla planning director Jeff Goodrich as CTO and third co-founder, and traces its system back to an early version built during Tesla's 2018 Model 3 production ramp.

Why: This is a funding announcement, not a product you can adopt: no pricing, no self-serve tier, no technical benchmarks, and the customers named are US enterprise brands. Treat it as a category signal that 'AI picks the inventory decision, not just forecasts it' is attracting capital, and note CEO Michael Rossiter's own framing is simulation plus path-finding over an infinite decision space — not a claim of measured accuracy. If you build logistics or ops tooling for Southeast Asian merchants, the useful takeaway is that the funded wedge is auto-execution on top of existing planning data, which is a harder trust problem than forecasting.

TechPowerUp's article is titled 'Micron CEO Says Memory Supply Will Be Much Tighter in 2027 and 2028 Than in 2026', but the fetched page returned a 403 Access Denied error, so no body text, quotes, figures, or capacity numbers are available. The only substantive signal is the Hacker News thread, which drew 231 points and 276 comments.

Why: There is not enough here to justify a decision. The headline asserts tighter memory supply in 2027 and 2028 versus 2026, but with no article body, no quoted CEO statement, no bit-supply or pricing figures, and no product categories named, you cannot tell whether this concerns DRAM, HBM, NAND, or consumer modules — or by how much. Anyone budgeting server RAM or GPU-adjacent hardware should treat this as an unverified headline, not a procurement trigger, until the primary source or Micron's own earnings commentary is read directly.

A The Hacker News DevSecOps/patch-management piece argues that financial services' long-standing habit of accepting a vulnerability backlog as a stability tradeoff no longer holds, because frontier models like 'Mythos' can read code and chain dormant weaknesses faster than teams can investigate and patch. It cites two figures: vulnerability exploitation has overtaken phishing as the leading initial access vector in financial services, and more than half of financial services vendors carry at least one high-severity CVE. The article names no vendor tooling, no version numbers, no remediation steps, and gives no methodology or source for either statistic.

Why: If you sell or integrate software into banks, insurers, or asset managers, this is a signal that your dependency-patching cadence is becoming a procurement and contract question rather than an internal hygiene one — 'we'll fix it in 18 months with a compensating control' is the exact posture the piece says is being repriced. Treat it as direction, not evidence: the two headline numbers (exploitation beating phishing; >50% of FS vendors with a high-severity CVE) are stated without a cited report, so don't quote them in a customer deck or a risk assessment until you find the underlying data.

PS3 emulator developers are warning buyers that counterfeit Blu-ray drives are being sold on Newegg and AliExpress, per Tom's Hardware. The article states scammers use spoofed firmware to make older drive mechanisms report as higher-end models inside premium-looking shells. The excerpt contains no model numbers, prices, seller names, or detection instructions beyond that warning.

Why: If you buy a Blu-ray drive for PS3 disc dumping or emulation, the drive's reported model ID is not trustworthy evidence of what's inside it — the source says firmware is being spoofed to disguise older mechanisms. That means a drive that identifies correctly in software can still be the wrong hardware, so the practical decision is to treat model-ID checks alone as insufficient and prefer sellers with return paths rather than the cheapest listing. For everyone outside retro-gaming hardware sourcing, nothing in this text requires a change.