NEAR AI Detects and Closes Internal-Systems Breach; NEAR Protocol Unaffected

NEAR AI Detects and Closes Internal-Systems Breach; NEAR Protocol Unaffected


NEAR AI said on November 10, 2026, that it had contained unauthorized access to its internal systems, fixed a vulnerability across its servers and restored its NEAR AI Cloud inference service. The company had temporarily suspended inference while investigating the incident and replacing affected credentials.

In a series of updates on X, the company said it had closed the unauthorized access before confirming that the service was back online. NEAR AI also said the vulnerability had been fixed on every server and affected credentials replaced. The company maintained that NEAR Protocol and its other services were not affected. It also pointed to the hardware-isolated Trusted Execution Environments (TEEs) used by NEAR AI Cloud, which are designed to protect customer prompts during inference.

NEAR AI detected unauthorized access, halted its Cloud inference service, and led the containment effort.

The unknown attacker exploited a server vulnerability, prompting NEAR AI to replace compromised credentials.

Intel’s TDX and NVIDIA confidential‑computing tech underpinned NEAR AI’s TEEs, shielding customer prompts during the breach.

However, NEAR AI has not yet published a detailed account of the incident or explicitly confirmed whether any customer information was accessed. It said a full incident report would follow.

NEAR AI’s Incident Timeline

NEAR AI disclosed the incident in a sequence of posts on November 10.

In its initial update at 04:44 AM IST, the company said it had identified unauthorized access to its internal systems and paused NEAR AI Cloud inference as a precaution while it investigated. It also stated that customer prompts were processed inside hardware-isolated TEEs and that NEAR Protocol and other NEAR services were unaffected.

In a subsequent update at 06:50 AM IST, NEAR AI said it had closed the unauthorized access but was still completing its investigation. The cloud service remained paused until the company could restore it safely.

The company later confirmed at 09:02 AM IST that NEAR AI Cloud was back online. It said it had fixed the vulnerability across its servers and replaced the affected credentials.

The updates establish that NEAR AI detected and contained unauthorized access, temporarily suspended inference, and then restored the service. They do not yet explain how the access occurred, who was responsible or which internal systems were reached.

Why the Incident Raises Questions About NEAR AI’s Privacy Model

NEAR AI Cloud is built around confidential inference: running AI models inside hardware-protected environments intended to prevent operators and infrastructure providers from accessing prompts and outputs.

According to NEAR AI’s technical documentation, its cloud service uses Intel Trust Domain Extensions (TDX) and NVIDIA confidential-computing technology. The company says inference runs inside these environments and that responses can include hardware-backed attestation evidence, allowing users to verify aspects of the execution environment.

NEAR AI has also described its integration with Intel Trust Authority, which adds an independent verification layer for Intel TDX attestation evidence. The Crypto Times previously reported on NEAR AI Cloud’s Intel-verified confidential inference.

That architecture is relevant to the incident, but it does not resolve every security question. Hardware isolation is designed to protect data processed inside an enclave. It does not, by itself, establish what happened to other internal systems, credentials, account information or operational data during an unauthorized-access incident.

The key issue is therefore whether the access was limited to systems outside the protected inference environment and whether the company can substantiate its position on customer-data protection.

What Is Known About Customer Data

NEAR AI has said that its inference service uses TEEs to protect customer prompts. It has not, in the three public incident updates, provided a specific finding that no customer data was accessed or exposed.

The company’s statement that it replaced affected credentials indicates that credentials it considered impacted were rotated. However, the updates do not identify the credentials involved, explain whether they were used by the attacker or specify the systems those credentials could access.

A distinction is important here: unauthorized access to internal systems does not automatically mean customer prompts or other user data were exposed. But the use of TEEs alone is not sufficient evidence to conclude that no customer information was affected.

Until NEAR AI publishes its incident report, the scope of the access and any potential data exposure remain unclear.

What NEAR AI Users Should Watch For

Customers using NEAR AI Cloud should review the company’s forthcoming incident report for details on the affected systems, the vulnerability, the credentials involved and whether the investigation found any customer-data exposure.

Users may also review their own API-key activity and access logs and consider rotating their credentials as a precaution, particularly if they use the service for sensitive workloads. This is a general security measure, not an indication that NEAR AI has reported customer API keys were compromised.

For NEAR token holders and users of the underlying blockchain, the company has repeatedly stated that NEAR Protocol and its other services were unaffected. That remains the company’s public assessment of the incident.

NEAR AI’s next substantive disclosure will need to clarify what systems the unauthorized party accessed, how the vulnerability was exploited and whether the company’s customer-data protections operated as intended. The Crypto Times will update this report when further details become available.

Also Read: Mercado Bitcoin Begins Gradual Platform Access After Security Incident


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *