Coding agents and CI runners install dependencies all day without a person watching, and that makes them an easy target for poisoned packages. GitHub’s answer is a package firewall that sits between those machines and the public npm registry, now in public preview for GitHub Enterprise Cloud customers.
The firewall inspects both metadata requests and package downloads and acts as what GitHub calls “an install-time policy gate.” Endpoints point at the firewall instead of going straight to upstream registries, and every request is checked against rules an administrator sets for the enterprise. GitHub announced the preview in a changelog post on Tuesday and rewrote the entry Wednesday “for clarity.”
The company tied the launch to “a recent flood of malware attacks that exploit systems at package installation time.” WebProNews reported last month on malicious npm packages that stole AWS keys and GitHub tokens, the kind of install-time attack this tool is built to stop.
What admins can set
The policy options at launch are a configurable cooldown period, checks against the GitHub Advisory Database for malware or vulnerability advisories, and supply-chain checks such as attestation downgrades.
GitHub said a user whose package is wrongly blocked can request an exception through a workflow similar to the one used in other GitHub Advanced Security features.
There are limits. The firewall supports only npm for now, so Python, Java and Go shops get nothing from it yet. It is open to GitHub Enterprise Cloud customers, including those using Enterprise Cloud with data residency. Setup steps are in GitHub’s documentation on protecting endpoints with package firewall.
The preview is free. GitHub said it will move to metered billing “similar to Actions billing” at general availability but has not published rates or a date for that switch.
Attackers were already probing for the PHP flaw known as PHP2Shell four days before it was supposed to become public, Amazon’s threat intelligence team said in a security blog post Wednesday evening.
The team found an exploitation attempt in telemetry from MadPot, Amazon’s network of honeypot sensors, dated Saturday, Oct. 17. The request came from an IP address tied to a commercial anonymization network. The two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were under embargo until 1400 UTC on Oct. 21, when PHP released fixed versions.
“While the vulnerability was under embargo, the targeting of a honeypot from an anonymized IP address suggests the activity was conducted by a threat actor, though it remains unclear how the actor acquired exploit information prior to disclosure,” Amazon wrote.
Exploits arrived before the patch
The timeline on disclosure day was just as compressed. Amazon said it saw multiple proof-of-concept exploits starting around 0200 UTC on Oct. 21, about 12 hours before the embargo lifted, and logged more attempts against MadPot from other anonymized infrastructure between 0200 and 0800 UTC. The payloads and infrastructure differed, which Amazon read as a sign of several separate actors. It also said its technical analysis is ongoing and that it is unclear whether those attempts would have worked against real systems.
Once the patch shipped, new exploits showed up within hours. Amazon now describes PHP2Shell as “broadly exploited in the wild.”
The post puts part of the blame for the shrinking gap on AI. “AI-assisted analysis makes it cheaper to turn a patch diff or advisory into a working exploit,” the team wrote, adding that more actors can now move within hours or even minutes of technical details coming out.
What Amazon tells defenders to change
For admins running PHP on internet-facing servers, Amazon’s advice starts with patching. Upgrading to the fixed PHP releases is the only complete remediation for both CVEs, and Amazon said no configuration-only workaround fully covers them. Teams that cannot patch right away can consider blocking multipart file uploads, after checking what that breaks, and should look for POST requests containing the PHP_SESSION_UPLOAD_PROGRESS string in form uploads.
Amazon also recommends starting PHP2Shell investigations from Oct. 17 at the latest rather than from the advisory date, and measuring patch timelines for critical internet-facing flaws in hours. “A 7-day or 30-day SLA assumes a delay that no longer exists,” the post said.
The blog lists six IP addresses seen in the activity, one from Oct. 17 and five from Oct. 21. Amazon cautioned that they belong to shared anonymization services and told organizations to investigate hits on them instead of blocking the addresses outright. A separate AWS post covers AWS WAF rules for PHP2Shell as a stopgap while servers are patched.
Amazon said its systems analyze more than 200 billion events per minute and use MadPot data to block known exploitation attempts in real time.
NVIDIA on Wednesday, Oct. 21, 2026, at GTC Berlin introduced DSX POD, a reference design for complete NVIDIA Vera Rubin AI factories that partners build inside modular containers, integrate and validate before shipment. At a prepared site, NVIDIA said deployment time falls from six months to as little as 14 days once power, cooling, networking and related utilities are ready. A global partner list is working toward worldwide delivery in early 2027.
Partners complete rack-to-rack cabling, wiring, piping and functional validation before shipment, moving that work into the manufacturing facility. The units arrive ready to connect to a prepared site’s power, cooling, networking and other supporting infrastructure. NVIDIA said that moves planning, construction, specialized labor and logistics off the traditional onsite build and reduces exposure to component delays and error-prone field work.
“An AI factory creates value when it starts producing tokens — not when construction is complete,” said Jensen Huang, founder and CEO of NVIDIA. “With NVIDIA DSX POD, we’re bringing factory-built precision and speed to AI infrastructure construction — reducing deployment time from months to weeks so customers can scale capacity and bring revenue-generating production online faster.”
Partners and the Berlin framing
NVIDIA named Anduril, Armada, Bull, Crusoe, DayOne, Dell Technologies, Delta, Eaton, Foxconn (Ingrasys), GIGABYTE, HPE, Lenovo, Pegatron, Quanta Cloud Technology (QCT), Schneider Electric, Vertiv and Wistron among the companies working to deliver DSX POD AI factories. The design carries forward the broader NVIDIA DSX infrastructure platform while packaging systems in purpose-built containers for transport and deployment.
In live keynote notes on the NVIDIA Blog, Huang cast DSX POD as a supply-chain shift: “This is a complete transformation of the world supply chain. This will change the way that people install and build data centers, and hopefully, as a result, velocity goes up.” The same keynote summary said the NVIDIA DSX AI Factory Platform can cut cooling water use by up to 100% and produce the same AI output with up to 30% less power — figures NVIDIA also used in its companion European DSX efficiency release the same morning.
My take: DSX POD is less a new chip than a logistics product — the same Vera Rubin stack, sold as a factory-tested container that starts earning tokens sooner. That sits next to other recent pushes to make AI infrastructure easier to stand up, including Google’s open-sourcing of TorchTPU and llm-d 1.0 for TPU inference on Oct. 20, 2026.
NVIDIA said partners plan to deliver DSX POD AI factories worldwide in early 2027.
NVIDIA on Wednesday, Oct. 21, 2026, at GTC Berlin announced the NVIDIA OpenShell Reference Architecture, a full-stack design for building, containing, observing and enforcing safe AI agents on enterprise infrastructure and at the edge. The company said the architecture is available now.
The design sits on NVIDIA OpenShell secure runtime software and pairs three hardware layers the company named in the release: NVIDIA Vera Rubin infrastructure for model inference (including closed and open models built with NVIDIA Nemotron), NVIDIA Vera CPUs for agent harnesses and tool use, and NVIDIA BlueField-4 DPUs running NVIDIA Sentry for continuous out-of-band monitoring and in-silicon policy enforcement. Edge coverage extends to NVIDIA RTX Spark, DGX Spark and DGX Station systems.
WebProNews covered the earlier open-source OpenShell runtime and Sentry hardware watchdog on Sept. 29, 2026. The new reference architecture extends that OpenShell runtime into full-stack infrastructure for agent development and operations, according to NVIDIA.
Layered containment and monitoring around an AI agent runtime. Illustration: WebProNews
What the stack claims to do
In the release, NVIDIA said Vera Rubin NVL72 systems deliver 30x higher throughput per megawatt for agentic workloads, Vera CPUs deliver 2x the performance of x86 processors with greater energy efficiency while running OpenShell, and BlueField with Sentry can quarantine an agent that moves outside its software boundary in milliseconds while boosting agent capacity by up to 20%. Those figures come from NVIDIA; independent benchmarks were not cited in the announcement.
“AI capability and safety must advance together,” said Jensen Huang, founder and CEO of NVIDIA. “As enterprises prepare to deploy billions of AI agents, safety and control must be built into the computing architecture. NVIDIA created OpenShell to give agents the freedom to do useful work within clearly defined boundaries — contained, monitored and under control. With the OpenShell Reference Architecture, agents can think on Rubin, act on Vera and be governed on BlueField.”
Huang made the same case in his GTC Berlin keynote, according to live notes on the NVIDIA Blog, where he described an agent as a model plus harness, sandbox, knowledge and tools, and said an agent’s privileges should be minimal and monitored. “Every single time an agent is launched, the privileges are different,” Huang said.
Who is wiring into it
NVIDIA said the architecture runs on Linux and Kubernetes stacks from Canonical, SUSE and Red Hat, and on Microsoft Windows using Microsoft Execution Containers — the MXC path WebProNews previously covered when Microsoft put policy enforcement around Windows agents. Cloud operating systems listed include Amazon Web Services, Google Cloud and Microsoft Azure.
NVIDIA said enterprises can run agents on OpenShell infrastructure from model builders including Anthropic, Cohere, Google, Meta, OpenAI, Perplexity, Reflection and SpaceX Super Intelligence. Cybersecurity vendors listed as integrating support include 1Password, Check Point, CrowdStrike, Cisco, F5, Fortinet, Microsoft, Okta, Palo Alto Networks, TrendAI and Zscaler. System makers Dell Technologies, Cisco, HPE, Lenovo and Supermicro are among those building infrastructure to the design, and cloud providers named include CoreWeave, Crusoe, Lambda, Nebius, Nscale, Oracle Cloud Infrastructure and Vultr.
On the application side, NVIDIA said SAP is integrating the architecture with Joule Studio runtime on the SAP Business AI Platform, and that Palantir is working with NVIDIA to deploy secure agents in production. Banks BBVA and Santander were named as exploring the architecture for agent safety and governance. NVIDIA’s release also said ServiceNow announced general availability of ServiceNow Arc, a personal long-running AI agent whose actions are governed at runtime by the ServiceNow Super Intelligence Control Tower and enforced by NVIDIA OpenShell.
The OpenShell Reference Architecture is available now, according to the Oct. 21 release.
ICANN leaders used the welcome ceremony of the organization's 2026 Annual General Meeting in Bali on Oct. 19 to promise faster work and more transparency about how it gets done.
"We need to strengthen the connection between strategy, prioritization, budgeting, and implementation, making the process clearer and more transparent," ICANN President and CEO Kurtis Lindqvist said, according to a CNW press release. "The ICANN community develops solutions and the ICANN org must turn those solutions into effective action."
In his speech, as reported by The Register, Lindqvist pointed to recent work on DNS abuse mitigation as proof the organization can move quickly. "That experience showed that we are responding with pace when the objective is clear, responsibilities are understood, and there is alignment around what needs to happen next," he said. "I would like us to bring that same discipline and rigor to more of our work."
The pledge builds on steps ICANN has taken for months. In a February blog post, Theresa Swinehart and Russ Weinstein introduced a Consolidated Scorecard Document that pulls information about community-developed policy and other outcomes into one place.
They tied the effort to ICANN's FY2026–2030 Strategic Plan, writing that ICANN is committed to building a culture of continuous improvement and excellence to better serve the global Internet community. The post pointed to existing pages for Enhancing ICANN Accountability Work Stream 2, which carries quarterly implementation reports, and for the IANA Naming Function Review 2.
ICANN also said it would begin publishing regular scorecards covering community policy activities in progress, recommendations before the Board and Board-adopted recommendations that ICANN org is implementing. Changes already underway included improvements to the Policy Outlook Report and closer internal tracking of action items from community meetings with the Board and CEO.
The reports cover a lot of ground: FY27 organizational objectives, policy work, review recommendations, financial and staffing metrics, action items for the Board and community groups, litigation and accountability mechanisms. The August 2026 report lists 154 Board action items completed and five in progress, with none not started.
An analysis by BTW Media noted that these are management status figures. They show where work sits between policy development, Board consideration and implementation, but they are not independent assurance of results.
ICANN87 in Bali
ICANN87 runs Oct. 17–22 and is the first ICANN public meeting held in Indonesia, co-hosted by the .id registry PANDI. It has more than 200 working sessions, covering topics such as DNS abuse mitigation, DNS security and the New gTLD Program.
Board Chair Tripti Sinha marked the tenth anniversary of the IANA stewardship transition. "A decade later, the strongest sign of success is what did not happen," she said, according to The Register. "DNS did not fragment. The coordination of unique identifiers was not destabilized. The internet continues to work."
She also warned that AI agents "could reshape DNS traffic patterns and intensify demand on the systems that enable discovery, authentication, and trust online," and said ICANN must deliver "governance capable of adapting to the speed of emerging risk."
ICANN has so far published Monthly Board Reports for July and August 2026 on its CEO Corner page.
China’s gross domestic product grew 4.5% from a year earlier in the third quarter. That beat economists’ median forecast of 4.4% and marked an acceleration from 4.3% in the second quarter.
Data from the National Bureau of Statistics released on Oct. 19 showed the pickup. It took expansion in the first nine months of the year to 4.6%. The figures put the economy on track to meet Beijing’s full-year target of 4.5%-5%.
The rebound comes after leaders rolled out measures to support home buyers and direct cheaper credit to infrastructure and technology sectors. Yet they have held back from large-scale stimulus. Exports of technology goods helped offset weak domestic demand and a prolonged property slump.
On a quarterly basis GDP rose 1.2%. That exceeded the 1.1% expected and compared with 0.9% growth in the prior period. The National Bureau of Statistics provided the sequential figure alongside the year-on-year data.
Analysts had pointed to solid export performance as a key driver heading into the release. Bloomberg reported the 4.5% pace dimmed prospects for additional easing measures in coming months. The first-nine-months 4.6% reading sits comfortably inside the government’s annual goal range.
But challenges remain. A property downturn now in its fifth year continues to weigh on investment and household wealth. Consumption has stayed muted even as some September activity indicators showed improvement.
The latest data eases immediate pressure on policymakers. They had vowed effective new policies earlier this year to counter soft domestic demand. Recent steps included mortgage subsidies for first-time buyers and targeted rate cuts.
Still, growth stayed below the 5% midpoint of the target band. The International Monetary Fund recently cut its forecast for China’s 2027 expansion to 4%, citing persistent headwinds in consumption and investment. No further details on additional stimulus emerged with the GDP release.
September industrial production, retail sales and fixed-asset investment figures came out alongside the GDP data. Those monthly indicators generally beat expectations and showed faster momentum than in August. The National Bureau of Statistics has not yet issued a full breakdown of third-quarter drivers beyond the headline growth.
Full-year growth is now projected near the lower end of the target. The Oct. 19 release marks the last major data point before authorities assess progress toward the 2026 goal in coming weeks.
A wheeled-legged robot built by Hangzhou-based DEEP Robotics went along on a biodiversity expedition in the Ailao Mountains of southwest China’s Yunnan Province. Company photos show the team working with the LYNX M20S on Aug. 28, 2026, in dense forest and on steep slopes.
Global Times called it the first real-world scientific exploration use of an embodied AI robot. The expedition, organized jointly by ifeng.com’s scientific exploration documentary program and the China Association for Scientific Expedition, focused on biodiversity research in a region known for its rich mix of species and hard terrain.
Support for Difficult Terrain
The robot worked in places that are difficult or unsafe for people to reach, handling route scouting, biological observation, image recording and supply transport, the company said in a statement sent to Global Times on Wednesday, Oct. 14. According to DEEP Robotics, the M20S has an IP67 rating for dust and water, runs in temperatures from -30 C to 55 C, and can carry a sustained 35-kilogram load with up to 3.5 hours of battery life.
Its most notable result was footage of Monotropa uniflora, known as ghost pipe, a plant that shows aboveground for only about 40 days a year, according to the expedition account. Chinese scientists said the footage adds important data for botanical research, Global Times reported.
The team also used the robot to film western black-crested gibbons, which live in old-growth forest at roughly 2,200 to 2,900 meters and are sensitive to human activity. Because the machine is small and quiet, researchers moved an observation point about 20 meters closer and recorded the gibbons leaping, foraging and calling.
Forest covers about 85.1% of the Ailao Mountains and vehicles can’t reach many sites, according to a DEEP Robotics press release distributed Oct. 17, so the robot also hauled imaging gear and small field supplies. The release described the trip as “a practical test of how mobile robotics can support biodiversity research in difficult-to-access environments.”
Li Jie, executive vice president of the China Association for Scientific Expedition, told Global Times the technology is bringing places that were previously inaccessible or impossible to observe continuously into the scope of scientific study.
Futurism was more skeptical on Oct. 18. It said photos show researchers “using the robot like a pack mule to carry field and imaging supplies,” suggested a human scientist could film the plant and gibbons just as well, and noted the M20S battery lasts 2.5 to 3.5 hours.
