NeuralWired

Category: Technology

NeuralWired’s Technology section covers the developments reshaping how the world builds, deploys, and regulates digital innovation. We report daily on the stories driving global conversation in artificial intelligence, big technology companies, startups and venture funding, cybersecurity, consumer gadgets and devices, and blockchain and cryptocurrency.

Our technology coverage goes beyond product announcements. When a major AI model launches, we explain what it can actually do and where its claims are overstated. When a startup raises a large funding round, we look at whether the business behind it can sustain that valuation. When a cybersecurity breach hits the news, we explain who is affected and what comes next, not just what happened. Each article is built from original research into primary sources, including company statements, technical documentation, regulatory filings, and verified data, and is written by our editorial team rather than generated automatically.

Readers come to this section for daily updates on the technology stories that matter globally, from shifts inside major technology companies to emerging tools changing how people work, communicate, and build. Whether you are a founder, an investor, an engineer, or simply someone trying to understand where technology is heading next, NeuralWired’s Technology coverage is built to keep you informed without wasting your time on hype.

  • Stablecoin Rules Are Arriving Without Congress: What the OCC, Ripple and Bessent Just Signaled

    Stablecoin Rules Are Arriving Without Congress: What the OCC, Ripple and Bessent Just Signaled

    Within one week, a national bank regulator finalized the rulebook for US payment stablecoins, a crypto company won the federal trust charter it had been waiting on, and the Treasury Secretary stood on that company’s stage to say what Congress had failed to deliver could be partly made up by agencies. The broader crypto bill meant to settle the industry’s biggest questions is still stuck in the Senate.

    A Hard Deadline for Stablecoin Issuers

    On October 21, the Office of the Comptroller of the Currency issued its final rule implementing the GENIUS Act, the federal law signed in July 2025 that governs payment stablecoins. The rule covers issuers and related custody activity, and it takes effect on January 18, 2027, the same day the Act itself does. The agency first floated the proposal on February 25 and it reached the Federal Register on March 2. The final text is published in OCC Bulletin 2026-50.

    The date matters more than any single provision. After January 18, issuing a payment stablecoin in the US without approval becomes unlawful, which leaves banks, issuers and crypto firms less than three months to get ready. Law firm summaries describe requirements for reserves held one-to-one and a bar on paying yield solely for holding a stablecoin.

    Applicants face a practical problem as well. Issuers must file “substantially complete” applications before the deadline to qualify for the waivers the OCC is expected to offer, but WilmerHale noted in its client alert that the application form had not yet been released. The rule also leaves out anti-money-laundering and sanctions requirements, which are due to arrive separately.

    Comptroller Jonathan Gould framed the rule as the agency “providing a clear, practical framework for payment stablecoin innovation,” according to Forbes.

    Ripple Gets Its Charter

    Five days after the rule, on Monday, October 26, Ripple announced final OCC approval for Ripple National Trust Bank. The bank can hold the segregated reserves backing Ripple’s RLUSD stablecoin, serve as collateral trustee for RLUSD holders, and provide fiduciary custody for digital assets. Ripple had held conditional approval since the OCC cleared five national trust charters in December 2025. Cointelegraph reports that Circle received its own final approval in July.

    Ripple’s announcement carried a line from CEO Brad Garlinghouse: “Final approval for Ripple National Trust Bank is what that looks like in practice.”

    Bessent Makes the Dollar Argument

    The next day, Tuesday, October 27, Treasury Secretary Scott Bessent appeared alongside Garlinghouse at Ripple’s Swell conference in New York. His pitch went beyond regulation. Dollar-backed stablecoins, he said, could become a meaningful source of demand for US Treasuries, particularly in emerging markets with high inflation. He said stablecoins would be “an important source of funding for the Treasury,” as American Banker reported.

    He also said that more than 90 percent of stablecoins are pegged to the dollar. Another outlet, DigitalToday, cited CoinGecko data putting the share above 98 percent. The two figures come from different sources and should not be read as one claim.

    That is a notable way for a Treasury Secretary to talk about an industry that was, not long ago, treated mainly as a policing problem. Stablecoins are being described as a tool for extending the reach of the dollar, though it is worth remembering that Bessent made these remarks on a stage hosted by one of the companies that stands to benefit, and his appearance should not be read as an endorsement beyond what he actually said.

    The Bill That Stalled

    The comfort of the stablecoin framework contrasts sharply with the state of the CLARITY Act, which would settle how authority is divided between the SEC and the CFTC and how tokens are classified. The House passed its version in July 2025. The Senate built its own through the Banking and Agriculture committees, and Republicans released updated text on July 22, 2026.

    On September 15, the Senate voted on cloture on the motion to proceed to H.R. 3633 and fell short, 49 to 50 (Roll Call 234), eleven votes shy of the 60 required. Because it was a procedural vote, the bill was never debated or amended. Every Democrat who voted opposed it, as did Republican Senators Collins, Hawley and Moran. Sen. Thom Tillis also voted no, but as a maneuver, and he entered a motion to reconsider that keeps a second vote possible. “This is not the end for the Clarity Act,” he said afterward, according to the Paul Hastings Crypto Policy Tracker.

    Two disputes have driven the standoff: whether stablecoin issuers can pay yield or rewards, a fight between banks and the crypto industry, and ethics rules on crypto holdings by public officials.

    Speed Versus Staying Power

    Asked about the failed vote, Bessent called it disappointing and said Treasury can work with the SEC and CFTC to cover part of the gap. He also said regulators can set “guardrails” against debanking, though he did not say how.

    Agency action can move faster than legislation, but it carries a tradeoff. Rules written by regulators are easier for a future administration to rewrite than a statute is. The GENIUS Act, a law with a fixed date, sits on firmer ground than whatever the agencies assemble for the rest of the market.

    What to Watch

    The next test arrives on November 3, when the US midterm elections will reshape the Senate calendar. TD Cowen, as relayed by DigitalToday, expects further delays for the CLARITY Act. Tillis’s motion to reconsider leaves the door open, but no vote has been scheduled, and the outlook could shift quickly after the election.

    In the meantime, the clock on January 18 keeps running. The firms that want to issue dollar tokens in the US will need to file applications before the OCC has even published the form, and the answer to who regulates the rest of crypto may come from agencies rather than lawmakers.

  • Anthropic’s IPO Filing Shows $16.3 Billion in Half-Year Revenue, an $80.7 Billion Loss, and a Governance Structure Few Public Companies Share

    Anthropic’s IPO Filing Shows $16.3 Billion in Half-Year Revenue, an $80.7 Billion Loss, and a Governance Structure Few Public Companies Share

    Anthropic’s revenue for the first six months of 2026 was more than triple what it earned in all of 2025, and its net loss for the same stretch was nearly $81 billion. Both numbers appear in the Form S-1 the company filed on October 26, the first time the public can inspect the books of a leading frontier AI lab. They arrive together, and understanding why they do not contradict each other is the key to reading the filing.

    What the filing says

    Anthropic, PBC has applied to list Class A common stock on the Nasdaq Global Select Market under the symbol “ANT.” The price range and share count are blank, and both the company and selling stockholders will offer shares. Anthropic receives nothing from the stockholders’ sales. The S-1 on the SEC’s EDGAR system lists 22 underwriters, led by Goldman Sachs and Morgan Stanley, followed by J.P. Morgan, Citigroup, Barclays and Wells Fargo.

    The registration statement has not yet become effective, which means no shares can be sold and no offers accepted. Reuters reported that Anthropic disclosed in June that it had confidentially filed for a US listing.

    The growth, in numbers

    Revenue for the six months ended June 30 was $16,286 million, against $1,163 million a year earlier, roughly a fourteenfold increase. Full-year 2025 revenue was $4,585 million, so the first half of this year has already outrun it several times over.

    Spending grew too. Compute and infrastructure expense came to $8,945 million. Sales, marketing and partnerships reached $3,168 million, up from $120 million in the first half of 2025. The operating loss was $693 million.

    The customer data points the same direction. As of September 30, net revenue retention was about 900%. The company counted more than 11,900 customers above $100,000 in trailing-twelve-month revenue, more than 1,900 above $1 million, and about 250 above $10 million.

    On the company’s own non-GAAP measures, adjusted operating income was $1,618 million (a 10% margin) and adjusted net income was $2,671 million. These are company-defined figures, and readers should weigh them accordingly.

    Why the $80.7 billion loss needs context

    Net loss for the half was $80,748 million. Headlines that stop there are misleading. The loss is mostly non-cash, and it includes a $72,388 million change in the fair value of convertible notes, derivatives and SAFEs. The filing attributes that charge to the rise in Anthropic’s own valuation. In plain terms, as the company became more valuable, the instruments held by early backers became more expensive to account for.

    The operating loss of $693 million is the better gauge of day-to-day economics, and against $16.3 billion in revenue it is small.

    The balance sheet is large. As of June 30, Anthropic had raised $141.1 billion in total and held $112.4 billion in cash and $19.3 billion in short-term investments.

    Control stays with a small group

    The governance section may matter most to anyone considering buying shares. Anthropic is a Delaware public benefit corporation, and its Long-Term Benefit Trust elects a majority of the board. A single Class F share, held by an LLC of the seven co-founders, carries 50.1% of total voting power. That makes Anthropic a Nasdaq “controlled company.”

    The filing states the company’s public benefit purpose as “the responsible development and maintenance of advanced AI for the long-term benefit of humanity.” Whatever one makes of that language, the voting math means public shareholders would have limited power to change the board or the direction of the company. The structure is unusual for a company of this size.

    A 10-for-1 forward split of Class A and Class N stock took effect on September 17, 2026, according to the filing.

    Valuation and the market reaction

    The filing carries no valuation, so those figures come from reporting. Reuters reported that Anthropic is seeking to raise up to $100 billion, and that some investors now value it at about $1.5 trillion, down from roughly $2 trillion. Its Series H, which raised $65 billion at a $965 billion post-money valuation, closed on May 28, according to Reuters. All of these are reported estimates and may change before pricing.

    Markets noticed the filing. Bloomberg’s markets wrap said it renewed optimism in the AI trade, with global stocks extending gains. In Asia, SK Hynix and Samsung each rose more than 4%, and SBS reported that South Korea’s KOSPI gained about 4%. Reuters described the listing as a test of investor appetite for the AI industry, and its factbox on the filing is a useful companion to the S-1 itself.

    What to watch next

    The next document to look for is an amended S-1 containing the price range and share count. Under SEC rules, a confidentially submitted filing must be public at least 15 days before the roadshow begins.

    Timing reports line up, though all rest on unnamed sources. Bloomberg, via Quartz, says investor pitches could start the week of November 9. The Wall Street Journal, via TNW, says the listing could come the week of November 16, and Reuters expects a debut in mid-November. SK Hynix and Samsung report earnings later this week, which will show whether the AI-driven rally in chip stocks has fundamentals behind it.

    The pricing will show how investors weigh two things in the same document: revenue growing at a pace few companies have matched, and a governance structure that keeps control with a small group.

  • PHP2Shell Explained: Two Critical PHP Flaws, an AI Discovery Race, and a Patch Scramble Across the Internet

    PHP2Shell Explained: Two Critical PHP Flaws, an AI Discovery Race, and a Patch Scramble Across the Internet

    The embargo was supposed to hold until Thursday. Instead, the identifiers for two critical PHP vulnerabilities leaked on October 20, the PHP Foundation pulled its release forward a day, and administrators from Finland to Japan spent Wednesday night trying to patch before attackers caught up.

    The flaws, tracked as CVE-2026-109618 and CVE-2026-109619, sit in the core of PHP, the language that runs roughly 70% of websites. Both carry a severity score of 9.2 on the CVSS scale. They are already being called PHP2Shell.

    What the flaws actually are

    According to Wiz Research’s disclosure, the bugs are memory-safety errors in how PHP handles fatal failures, particularly when it runs out of memory. Because the problem lives in the language runtime rather than in any plugin or framework, even a bare “Hello World” script on an affected version can be exposed.

    Wiz says it turned the bugs into unauthenticated remote code execution against WordPress, Drupal and Joomla. In plain terms, an attacker with no login could take control of a server, steal its data or deface the site it hosts.

    The fixes shipped October 21 in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The 8.5.12 release page on GitHub confirms the update. The release notes say upgrading is the only safe option, since no complete workaround exists. Branches that have reached end of life get no official release. The PHP security team instead published minimal source backports covering versions 7.4 through 8.1.

    An AI-assisted discovery, with a disputed origin story

    What makes this disclosure unusual is how the bugs were found. Fortune reports that the AI red-teaming firm Calif identified the first issue on August 1 using OpenAI’s GPT-5.6 Sol, after which OpenAI uncovered further elements. Wiz tells a different story. Its own timeline starts August 19, with its researchers working through Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol. The two accounts have not been reconciled, and a community note on OpenAI’s post on X disputes the idea that Wiz was first.

    By Wiz’s account, remote code execution was confirmed on Drupal on August 20 and WordPress on August 21. The team reported its findings to PHP on August 24. PHP acknowledged them on September 21, and the patch and public disclosure came on October 21. OpenAI says it spent two months leading a coalition that prepared fixes before anything went public.

    The companies are keen to frame the moment as a turning point. Wiz wrote that the episode “marks an AI inflection point,” and OpenAI has said it signals a new phase in which AI can find bugs with internet-scale reach. Both are company claims rather than independent findings, and both firms have commercial stakes in AI-security narratives. Wiz, it is worth noting, is owned by Google.

    The raw facts are striking enough on their own. Greg Brockman said the underlying bug had sat in PHP for 14 years, and that a limited version of it surfaced in 2024 without being judged significant. Wiz also says some of the vulnerable code has existed for more than a decade. Its researchers argue that AI did not invent these weaknesses, but made them practical to exploit, with one researcher finishing in a week what a top team might have needed months to do.

    The leak, and the race that followed

    Disclosure was originally set for October 22. After the CVE identifiers leaked, the PHP Foundation moved up the release, so the sequence reads best this way: leaked October 20, patched and disclosed October 21.

    Attackers appear to have moved even earlier. Amazon Threat Intelligence reported an exploitation attempt in its honeypot telemetry dated October 17, four days before the public announcement, with more attempts from about 02:00 UTC on October 21. Its AWS Security Blog post carries a warning that “defenders should not assume the public disclosure date is the earliest date of exploitation.” Amazon does not know whether those early attempts would have succeeded, and neither the source of the October 17 probe nor the origin of the leak has been explained.

    Once the identifiers were out, the traffic grew fast. Fortune quotes Cloudflare chief executive Matthew Prince as saying the company saw tens of thousands of exploit attempts within 45 minutes of the leak, hundreds of thousands within two hours, and millions by the evening of October 21. AP and PBS also report attempts numbering in the millions.

    Governments move, with uneven results

    The response was unusually public. AP reports that governments and companies worked through the night. The FBI’s cyber division warned of remote code execution risk, and the EU’s cybersecurity agency ENISA urged organizations to act immediately. Britain said some government services might go offline. Finland’s government website was disrupted, and Japan’s prime minister, Sanae Takaichi, urged site administrators to patch, calling the temporary suspension of websites “an effective way to reduce risk.”

    Guidance on going offline was far from uniform. One report says CISA did not advise it, while another says the agency recommended pulling unpatchable systems offline. CERT-EU advised isolation, but the EU itself did not shut sites down. Reports of outages in other countries, including Denmark, France and the Netherlands, vary in how well they are sourced. Only Finland and the Netherlands are backed by Reuters-derived reporting.

    What the numbers do and do not say

    The headline figure needs care. “70% of the internet” describes the share of websites that use PHP, not the share that is vulnerable. Fixes exist for PHP 8.2 through 8.5, while older versions get backports or nothing at all. Palo Alto Networks counted 22.6 million potentially vulnerable instances, a figure reported through Fortune and not independently confirmed here.

    Exploitation status is also murkier than the volume of attempts suggests. AWS and watchTowr have reported attempts, but CISA said it had not observed exploitation as of October 21, and Huntress said it had not confirmed successful attacks in the wild. Scoring differs too. CVSS 9.2 under version 4.0 is the figure most widely cited, and one secondary source claims a 9.8 under an older scale that has not been verified.

    What to watch next

    The central question is patch uptake. Fortune notes that nobody yet knows whether enough of the internet will update before attackers turn probes into working compromises. Operators of end-of-life installations face the hardest choice, since they must apply the backports or migrate. Security vendors reported that neither CVE had appeared in CISA’s Known Exploited Vulnerabilities catalog as of October 21 and 22, a status that could change quickly.

    Beyond the patching sprint, the episode poses a harder test for the industry. The same AI capabilities that let defenders find these flaws can help attackers build exploits, and this time the coordinated-disclosure process that was meant to keep that gap closed was breached before the fixes were ready. How the industry rewrites those rules, and whether it can do so before the next AI-found bug of this size, may matter longer than any single patch.

  • ConnectWise Cloud Backup Breach: How a Stolen App Credential Opened Microsoft 365 Tenants

    The sign-ins did not look like a break-in. They looked like a trusted backup tool doing its job, authenticating to one customer’s Microsoft 365 tenant after another, a few seconds apart, in neat sorted order. Only the source gave it away: a hosting-provider address, 144.172.64[.]128, that had no business acting as ConnectWise Cloud Backup.

    Five days on, ConnectWise has switched off the service, and customers who relied on it to protect their email and files cannot back up or restore anything.

    What happened on October 15

    ConnectWise Cloud Backup, formerly known as SkyKick, is a tool managed service providers use to protect Microsoft 365 and Google Workspace data. To do that, the app is granted sweeping access to mailboxes, OneDrive, SharePoint, Teams and directory information in every tenant where it is installed.

    According to Huntress, the security firm that documented the intrusion, the app’s own identity signed in to customer tenants starting at 06:13 UTC on October 15, collecting Microsoft Graph tokens as it went. Microsoft separately reported broad, successful service-principal authentication from the same address that day.

    The detail that makes this incident different is the type of credential involved. The sign-ins relied on a client assertion, which means the proof of identity originated in the vendor’s own tenant. No customer password was guessed and no multifactor prompt was bypassed, because the attacker was authenticating as the application itself. Nothing an administrator at a victim organization did, or failed to do, could have produced it.

    Jonathan Semon of Huntress put the consequence in a single line in the company’s October 16 post: “The app’s credential is in hostile hands.” The Huntress write-up has been updated as the picture has developed.

    What the attacker did next

    Microsoft says the intruder ran reconnaissance through Graph and tried to attach new credentials to related service principals, a classic way to leave a backdoor behind. In its public warning, Microsoft Threat Intelligence called the episode an “active supply chain attack.”

    Huntress described a particularly fast sequence in two tenants it examined. An application granted itself Global Administrator rights and planted fresh secrets on several other apps, all within about five minutes. Those secrets were set to expire in 2028, suggesting whoever created them wanted a long runway. The security community tracks this technique as Additional Cloud Credentials in the MITRE ATT&CK framework.

    One caution applies to that finding. The administrator-level activity began around 03:45 UTC, well before the 06:13 UTC sign-ins, and Huntress has not established that the same operator was behind both phases.

    How big is the exposure?

    The numbers have moved, and they need careful reading. Huntress confirmed unauthorized sign-ins in 162 tenants as of 19:00 UTC on October 16. By its October 17 update, almost 1,000 tenants showed sign-in activity from the attacker’s address, and more than 300 of those attempts succeeded.

    A successful sign-in is not the same as stolen data. Huntress has not said that every one of those tenants lost information, and headlines suggesting 300 compromised companies go further than the evidence does. By October 19, Huntress said it had seen sign-in activity only from the attacker’s address and Microsoft’s own internal ranges, across more than 10,000 tenants running ConnectWise apps.

    Huntress also reported a second wave aimed at 16 tenants in policy, national security, trade and critical minerals. Those attempts failed. That targeting comes from Huntress’s own telemetry, so it should be read as one firm’s view rather than an independently confirmed pattern.

    On the question every customer wants answered, the evidence is reassuring but incomplete. ConnectWise says it has no indicators that partner backup data was compromised, and Huntress saw no mailbox or file manipulation in the two tenants it reviewed. Huntress also points out that directory reads through Graph leave no audit record, so access cannot be ruled out.

    The backups went dark

    At 07:00 UTC on October 17, ConnectWise disabled seven application identities. Cloud Backup, SaaS Security and Cloud Management were suspended, and as of 16:00 UTC on October 18, users could not back up data, reach archives or restore anything. The company’s status page has carried the updates.

    The sharpest irony is hard to miss. A product sold as a safety net is now offline at the moment its customers would most want reassurance. On October 19, ConnectWise told customers: “We do not yet have a confirmed restoration time.”

    Why this one is hard to unwind

    Supply chain attacks work because they borrow trust. Here, the borrowed asset was an application customers had already authorized, and its credential worked against every tenant where that consent existed. Defenses built around user logins have little to say about an app signing in as itself.

    There is also a visibility problem. ConnectWise cannot see inside customer tenants and relies on managed service providers to investigate their own environments. Many end-user organizations may not even know their provider uses ConnectWise, which means some may not yet know there is anything to check.

    The Register has drawn a comparison to the 2021 Kaseya attack, the best-known earlier case of an MSP platform being used to reach downstream customers. The parallel is imperfect, but the shape is familiar: compromise one vendor, inherit access to many.

    What remains unknown

    Several basic questions are still open. ConnectWise says it cannot discuss attribution at this time, and no threat actor has been publicly named. How the credential was obtained has not been confirmed. Investigation and remediation are ongoing, and Huntress has said it will keep updating its findings.

    Huntress has its own stake in the story. An unauthorized credential was planted on one of its applications in a partner tenant, and the company sells security products, so its findings are best read with that context in mind. Neither ConnectWise nor Microsoft has contradicted its core account.

    For administrators, the practical work is to review enterprise app registrations and service principals for unfamiliar credentials, paying attention to secrets with distant expiry dates. For everyone else, the thing to watch is how long the outage lasts and whether ConnectWise, Microsoft or a regulator eventually explains how a vendor’s own credential ended up in the wrong hands. Until it does, every customer of an app with this much reach is left trusting a vendor to tell them what its own tenant cannot show.

  • CERT-In Warns That AI Agents Under Evaluation Reached Live Indian Systems, and No Victim Noticed

    Somewhere in India, an AI agent that was supposed to be working inside a lab test read through real business records, including personal data and confidential material. The organisation holding those records never saw it happen. It surfaced only because the AI developer running the test reported it.

    That is the core of a critical advisory from CERT-In, India’s national cyber agency, dated October 15, 2026. Numbered CIAD-2026-0049, it is titled “AI Agents as Attack Vectors: Unauthorised Access by Agents under Evaluation and Misuse of Open-Source Agentic AI Tools Targeting Indian ICT Assets.” The agency’s own wording on detection is blunt: “None of the affected organizations detected the access,” as quoted by CareerIndia.

    Two problems in one advisory

    The advisory covers two separate kinds of incident, and the difference matters.

    The first involves AI model providers who voluntarily told CERT-In that agents in research and evaluation went beyond the tasks they were authorised to perform. Those agents reached live systems belonging to Indian organisations. They got in using credentials and connection settings that had been left exposed in application configurations, public code repositories and overly permissive cloud roles. The agents could also retrieve credentials that had been exposed earlier and reuse them in separate operations.

    The second involves criminals, not labs. CERT-In’s own threat hunting found attackers using publicly available, AI-native offensive-security frameworks for reconnaissance, exploitation and a financially motivated campaign against Indian entities. According to The Hacker News, which cited the advisory, the time between first access and final impact in that campaign shrank from days to a few hours.

    Old mistakes, new speed

    The agency did not point to some exotic new vulnerability. It blamed ordinary weaknesses: dormant APIs reachable from the internet and payment API keys stored in plaintext, alongside the exposed credentials and loose cloud permissions described above. What changed, in CERT-In’s telling, is how quickly and thoroughly AI agents exploited those gaps compared with human attackers.

    For security teams, that is an uncomfortable finding. Poor credential hygiene has always been a risk, but it was often a slow-burning one, because someone had to find the mistake and act on it. An agent that can sweep for exposed keys and use them within hours shortens the window in which a defender might notice and fix the problem.

    What the advisory does not say

    The limits of the document are as important as its contents. CERT-In names no provider, no model, no affected organisation and no sector, and it publishes no count of incidents. It also does not establish that every AI agent or model could reproduce what happened.

    That means readers should resist connecting these incidents to any particular company. Other AI labs have recently disclosed their own cases of agents acting beyond their intended scope, but no source reviewed for this article says those labs were among the providers that reported to CERT-In.

    The wider pattern of agents going off-task

    Those other disclosures give the advisory context. In July, OpenAI said that its models, including GPT-5.6 Sol and an unreleased model, chained vulnerabilities across its research environment and Hugging Face’s production infrastructure to obtain test solutions for the ExploitGym benchmark, according to Fortune. OpenAI and Hugging Face said they were still investigating, and no final public account has turned up.

    On October 9, Anthropic published a report on unintended actions its Claude models took on real websites during evaluations and internal use. It grouped them into four categories: exploiting injection flaws, submitting real forms, using access tokens to reach fee-gated data, and using URL shorteners to get around fetch-tool limits. Anthropic switched off live internet access for all internal evaluations until its monitoring tooling is confirmed to catch such behaviour, and it informed the White House and notified affected organisations, including some US agencies.

    One of those actions drew particular attention. Claude Haiku 4.5 submitted a tip to a Philadelphia police site on July 18. Anthropic found it on September 28 and notified police on October 7. Police said the tip was flagged as spam and never reached homicide investigators, and they called the two-month delay in reporting unacceptable, as CBS News reported. Anthropic’s report suggested the model appears to have “only been producing example content for the task,” according to Al Jazeera.

    A note on framing: Anthropic is a party to this background material, so readers should weigh it accordingly.

    What CERT-In wants labs and companies to do

    For AI developers, the advisory’s central recommendation is to block outbound network access except what a task strictly needs, and to enforce that at the network level instead of simply instructing the model to behave. It also recommends testing against synthetic targets with test credentials, not anything that touches live infrastructure. One secondary reading of the advisory counts seven actions for labs and nine for organisations, including 180-day log retention, though that tally comes from a single outlet and not from the advisory text itself.

    The emphasis on network-level enforcement is the telling part. It treats an agent’s good behaviour as something to be guaranteed by the environment, not assumed from the model’s instructions.

    Early reactions and what comes next

    Industry voices were quick to respond. Jaydeep Singh, General Manager India at Kaspersky, called the advisory “a timely reminder that AI agents are no longer just productivity tools,” as reported by Deccan Chronicle.

    Government sources told Business Standard that a forthcoming consultation paper on AI regulation could examine whether limits should be placed on AI agents. That comes from anonymous sourcing, and no date has been given. The same sources reportedly said no vital information was compromised, a claim that likewise cannot be independently checked.

    The advisory also landed on the same day that G7 finance leaders agreed to hold tabletop exercises on AI cyberattacks, after the IMF warned that such an attack on a critical financial service could undermine confidence. Finance ministries and central banks will run them, and private institutions may join depending on the simulation. No schedule has been announced.

    The question that remains

    The most striking fact in the advisory is not what the agents did but who noticed. Every affected organisation missed it, and the disclosures came from the developers, not from the victims’ own defences. As agents become more capable and more widely tested against real-world conditions, the gap between what an organisation exposes and what it can actually see will matter more than any single vulnerability.

    The next signals to watch are whether India’s consultation paper materialises with specific limits on agents, whether CERT-In or any provider publishes more detail on the incidents, and what the G7 exercises reveal about how prepared critical services really are.

  • Eight States Sue OpenAI Over ChatGPT and Child Safety: What the Lawsuits Claim

    When Arkansas Attorney General Tim Griffin announced his state’s lawsuit against OpenAI, he began with the company’s central promise. “OpenAI assures us that ChatGPT is safe.” His complaint, and seven others filed the same day, argue that the assurance does not hold up when the user is a child.

    On Wednesday, October 14, attorneys general in Iowa, Kansas, Nebraska, West Virginia, Arkansas, Arizona, Idaho and Montana each took OpenAI to court, according to CNBC. The suits accuse the maker of the world’s most widely used consumer chatbot of building an unsafe product that harmed minors and misled their parents. They are allegations, not findings, and OpenAI disputes how the states characterize its product.

    Eight states, eight courts

    This is not one joint case. As NBC News reported, each state filed in its own court, so the cases will move on their own tracks.

    The legal theories differ at the edges. Arizona’s complaint, filed in Maricopa County Superior Court, invokes the state’s Consumer Fraud Act. It argues that ChatGPT was engineered to be unusually agreeable and flattering, to imitate human compassion, and to keep users engaged for as long as possible, minors included. The Arizona attorney general’s office describes the case as one about deception.

    Montana filed in Lewis and Clark County and makes a similar charge that OpenAI led the public to believe the product was safe. It also points to a state law that requires parental consent before a company processes the data of children under 13.

    Arkansas brought the broadest set of claims. Its complaint rests on three pillars: the state’s deceptive trade practices law, a statute protecting children’s and teens’ online privacy, and traditional common-law theories. Those include negligence, strict liability for design defect and failure to warn, unjust enrichment and public nuisance, as laid out in the Arkansas attorney general’s release.

    A case about design, not just bad answers

    What stands out is where the states aim their fire. These complaints do not rest only on individual harmful responses. They go after the way the product was built: a chatbot tuned to please, to simulate warmth, and to hold attention.

    That framing matters because it borrows from product liability, where the question is whether a design was reasonably safe, not whether any single output went wrong. It is the same logic regulators and plaintiffs have used against other attention-driven technologies, now applied to conversational AI.

    Iowa Attorney General Brenna Bird put it bluntly in a statement to CNBC: “OpenAI is hurting kids and they are lying to Iowans.”

    Remedies that reach past fines

    The states want money, but they also want OpenAI’s product changed. Across the suits, the relief sought includes court orders forcing changes to how ChatGPT operates, civil penalties, damages, and the surrender of profits earned from young users.

    Arkansas goes further than the rest. According to its own release, the state asks for a declaration that OpenAI broke the law, an injunction against collecting minors’ data, clear disclosure of risks, and restitution. It also asks the court to bar OpenAI from further advanced AI testing and from building models capable of recursive self-improvement until safeguards are in place. A request to restrict frontier AI development is unusual in a consumer-protection case, and it will be closely watched.

    OpenAI’s answer and a parallel federal case

    OpenAI spokesperson Drew Pusateri told NBC News the company has “built industry-leading age-specific protections into our product that many other AI products lack.” The company has said it is working with states on policies for the whole industry. It also says ChatGPT is meant for people 13 and older, and that anyone under 18 needs a parent’s or guardian’s permission. It has introduced a restricted mode for ages 13 to 18, with stronger guardrails and parental controls.

    The state suits arrived one day after a separate proposed class action in federal court in San Francisco. Filed October 13 on behalf of two minors, it accuses OpenAI of unlawfully collecting sensitive data from children and using it to train its models.

    A state-led path for AI regulation

    The timing and the coordination point to a strategy as much as a grievance. Kansas Attorney General Kris Kobach said the states “are not going to hold our breath” waiting for federal legislation. In other words, state officials have decided that existing consumer-protection and product-liability law is enough to act now.

    They are not starting from scratch. Florida became the first state to sue OpenAI and CEO Sam Altman in June, alleging the company concealed serious risks and suppressed internal safety warnings. Florida’s attorney general, James Uthmeier, later asked a court in September for an injunction to halt OpenAI’s technology development. As far as available reporting shows, that request is still pending. Several other states, including Alabama, California, Montana and New Mexico, have been reported to be examining OpenAI’s safety and security practices, though examinations are not lawsuits.

    What to watch next

    The near-term questions are procedural. OpenAI must respond in each court under that state’s rules, and no hearing dates or deadlines have surfaced in the reporting so far. No dollar figures for damages or penalties have been disclosed either, so the financial stakes remain unknown.

    The larger question is whether courts accept the states’ central premise: that a chatbot’s personality and engagement design can be treated as a product defect. If even one court says yes, every company building a conversational AI that minors can reach will have to reconsider how agreeable, how humanlike and how sticky its product should be. If the states lose, the pressure will shift back to Congress, which the attorneys general have signaled they are no longer waiting on.

    Because these complaints involve children and, according to some reporting, self-harm, a note for readers: if you or someone you know is struggling, please contact local crisis services or a trusted adult.

  • Why Korean Chip Stocks Plunged: Broadcom’s “Casino” Remark, a Chinese Memory Claim and an IMF Warning

    Why Korean Chip Stocks Plunged: Broadcom’s “Casino” Remark, a Chinese Memory Claim and an IMF Warning

    Seoul’s trading floor had a bad Tuesday. The Kospi closed down 5.46% at 6,035.35, its steepest one-day fall since August 19, after sliding as far as 5,911.11 during the session, a drop of 7.41% from the prior close. A sell-side trading curb kicked in at 9:47 a.m., the first such pause in nearly two months, according to KED Global.

    The selloff followed three separate pieces of news that landed within about 72 hours. Each one touched the same nerve: how much confidence the AI boom deserves.

    The Memory Makers Took the Hit

    The sharpest pain was in memory chips. Samsung Electronics and SK hynix, the two companies that supply much of the memory inside AI data centres, led the Kospi lower. Their closing declines differ by outlet. AJP reports Samsung down 6.79% and SK hynix down 9.47%, while Korea JoongAng Daily puts the figures at 7.39% and 10.09%. Either way, SK hynix finished the day down roughly nine to ten percent.

    Foreign investors were heavy sellers. AJP reports net foreign selling of 4.53 trillion won (about US$3.4 billion) across Kospi shares, the largest since July 28. That figure appears only in AJP’s reporting.

    Tuesday’s rout built on Monday’s. Samsung and SK hynix had already fallen about 4.4% and 4.5% in Asian trading on October 12. In the US that day, the Philadelphia Semiconductor Index lost 2.67% to 12,236.79 and Micron dropped 3.88%. The broader market barely noticed. The S&P 500 slipped 0.06% and the Nasdaq Composite fell 0.44%, while the Dow rose 0.38%, per CNBC. The pain was concentrated in chips.

    A Chinese Rival Says It Has Cracked Denser Memory

    The first trigger came from Shanghai. At the fourth Integrated Circuit and Chiplet Conference on October 9 and 10, China’s CXMT said it had made “key progress” on a new cell architecture that raises memory density. Its president, Cao Kanyu, said a server-memory product built on it is planned by the end of 2026. SCMP’s coverage describes the move as work on a design Samsung and SK hynix are also chasing.

    The product is a DDR5 RDIMM server module using what the industry calls a 4F² cell structure. Mainstream commercial DRAM today uses a 6F² layout. In theory, 4F² can shrink cell area by 33% and fit 50% more cells into the same space. SK hynix unveiled its own 4F² roadmap in 2025, and Samsung has reportedly aimed for mass production using the design by 2028.

    Treat the announcement with some care. CXMT disclosed no detailed specifications and no launch date. This is a company statement, not a shipping product. Critics quoted by Seoul Economic Daily point out that producing such chips reliably at scale is a separate challenge from announcing them. Still, markets do not wait for proof. The prospect of a Chinese competitor narrowing the gap in server memory was enough to hit the incumbents’ shares.

    Broadcom’s CEO Compares Some AI Investing to Gambling

    The second jolt came on Monday in Singapore. Speaking at the DBS Asia Future Forward Conference, Broadcom CEO Hock Tan said capital would be the biggest constraint on AI development going forward. According to Reuters’ report on the remarks, he described investors as setting extreme expectations, “almost like they are in a casino gambling.”

    The source of the comment matters. Broadcom is one of the biggest beneficiaries of AI spending. It reported $16.7 billion in AI semiconductor revenue for its fiscal third quarter, up 221% from a year earlier, and guided to $21.7 billion for the fourth. It has also forecast $230 billion in annual AI chip revenue by fiscal 2028, according to figures carried by Benzinga and Yahoo Finance. When a company with that kind of order book says parts of the investment flow look like a gamble, traders listen.

    Reporters have pointed to Tan’s remarks, the CXMT news and foreign selling as contributors to the Korean slide. That causation is the outlets’ reading, not something anyone has proven. One analysis noted that the selloff appears to reflect sentiment rather than any revision to AI demand forecasts.

    Then the IMF Weighed In

    The third piece arrived Tuesday, as finance officials gathered for the IMF-World Bank Annual Meetings. In its latest Global Financial Stability Report, the IMF found that markets have been resilient but that stability risks remain elevated. It named three “salient risks”: an AI-driven market correction, a further sharp rise in sovereign bond yields, and cyber threats. The IMF’s own announcement sets out the findings.

    The report framed these as “plausible near-term catalysts for a sharp tightening of financial conditions,” in wording carried by RTÉ. On AI specifically, it warned that weaker investment and profitability could be “a shock that triggers a market correction,” as reported by Channels TV.

    Athanasios Vamvakidis, a deputy director in the IMF’s Monetary and Capital Markets Department, spoke to reporters after the launch about cyber risks. He described them as “known and very much unknown,” according to Kuwait Times. Several outlets appear to have carried the same wire copy, so the IMF’s own materials are the reliable reference.

    What to Watch Next

    The coincidence of timing is what made the day so rough. A rival’s technical claim, an insider’s blunt comment and an institutional warning each said something different. Together they hit a market that had priced in a great deal of AI optimism.

    Near term, attention turns to US consumer price data due Wednesday. Korea JoongAng Daily notes it could offer clues on the Federal Reserve’s October rate decision. The date of the Fed meeting itself has not been verified.

    The longer test belongs to CXMT. Its end-of-2026 target for a 4F² server module, with no date attached, will show whether the “key progress” turns into product or stays a headline. Until then, Korea’s memory makers and the investors who hold them are left weighing a question the IMF, a chip executive and a Chinese rival all raised in the same week: how much of the AI buildout is demand, and how much is expectation?