NEAR AI discloses SGLang security flaw, revokes two exposed API keys
NEAR AI disclosed a security incident involving an SGLang remote-code-execution vulnerability in legacy deployment infrastructure. The November 9 report states that approximately 100 user details and 18 agents were identified in the affected context, with two Cloud API keys exposed and revoked. The company found no evidence that stored Private Chat content was compromised, while noting that some requests made on November 8 could have been observed. The report distinguishes confirmed exposure from categories of access for which there is no evidence.
The problem was in the service stack
SGLang is infrastructure used to serve language models within a broader service stack that includes model servers, routers, authentication, logging and the user-facing application. A vulnerability at this layer can enable attacks before users interact with onchain wallets or sign transactions. Remote-code execution can allow unauthorized instructions to run within the affected environment. Impact depends on that environment’s privileges, network reach and available data. The incident does not involve NEAR blockchain consensus rules or a general compromise of NEAR wallets. It concerns specific AI-serving infrastructure and its potential exposures.
NEAR AI’s reported response
The team investigated affected deployments, revoked the exposed API keys, remediated the vulnerability and notified impacted parties. Effectiveness depends on closing all pathways and rotating credentials wherever they were used. Numerical counts require careful interpretation: roughly 100 user details and 18 agents in context do not imply that 100 users lost funds or that every request was accessed. Exposure, confirmed access and financial loss are separate findings.
Why crypto and AI security overlap
Crypto firms increasingly use AI for development, support, trading and operations. AI tools can handle sensitive business information even when they cannot sign onchain transactions. Safeguards remain critical: isolating services, limiting credentials, monitoring access and maintaining incident-response plans. Institutional adoption of blockchain infrastructure, including the NYSE’s tokenized-securities plans, requires robust offchain services in addition to secure smart contracts. A well-audited ledger cannot offset a compromised application server. Rising institutional attention to crypto assets, tracked through developments such as Ether ETF flows, increases the importance of operational controls. These links provide context and do not imply involvement of those products in this incident.
Implications for users and next steps
Affected users should follow NEAR AI’s notifications and guidance. Where credentials intersect related services, review access and rotate keys. Ordinary NEAR wallet keys should not be assumed exposed based solely on this infrastructure flaw. A detailed technical postmortem remains important: affected versions, root cause and validation of fixes.
Written by the News Desk and edited by Samuel Rae.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.
