LogoLMSpeed

A deep API relay audit for Xinjianya API DeepSeek V4 Pro

This is not a simple speed test. It is a deep LMSpeed audit designed to expose API relay risk: model swaps, hidden prompts, token injection, context truncation, rewritten tool calls, error leakage, and broken SSE streams. Run your own API through the same audit and see whether it is safe to ship.

Audit result

Checked
Jul 7, 2026, 1:30 AM
Duration
1080.7s
Target
new.xinjianya.top
Provider
Xinjianya API
Model
DeepSeek V4 Pro
Auditor
lmspeed.net

Check health scores

0-49 risk found50-79 review risk80-100 healthy
72

Model authenticity

72

Prompt and instruction

80

Response integrity and stability

100

Endpoint profile

72

Model authenticity

Inconclusive

Checks whether requested model family, identity response, context capacity, and stream model name line up.

Instruction conflict

Instruction conflict runtime error

Inconclusive

Inconclusive

Plain-language meaning

Instruction conflict did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Context window

Context window runtime error

Inconclusive

Inconclusive

Plain-language meaning

Context window did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Stream integrity

Stream integrity runtime error

Inconclusive

Inconclusive

Plain-language meaning

Stream integrity did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

72

Prompt and instruction

Inconclusive

Checks hidden prompt injection, prompt extraction, jailbreak leakage, and Web3 injection risk.

Token injection

Token injection runtime error

Inconclusive

Inconclusive

Plain-language meaning

Token injection did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Prompt extraction

Prompt extraction runtime error

Inconclusive

Inconclusive

Plain-language meaning

Prompt extraction did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Jailbreak and identity leakage

Jailbreak and identity leakage runtime error

Inconclusive

Inconclusive

Plain-language meaning

Jailbreak and identity leakage did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Web3 prompt injection

Web3 prompt injection runtime error

Inconclusive

Inconclusive

Plain-language meaning

Web3 prompt injection did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

80

Response integrity and stability

Inconclusive

Checks whether the return path rewrites package-install commands, whether error responses leak internal details, and whether latency variance suggests multi-routing or queueing instability.

Tool-call substitution

Tool-call substitution runtime error

Inconclusive

Inconclusive

Plain-language meaning

Tool-call substitution did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

Error response leakage (AC-2)

Error response leakage

Passed

Passed

Plain-language meaning

Sends broken requests and scans error bodies/headers for API keys, upstream URLs, environment variables, paths, or stack traces.

Audit evidence

See the structured evidence and redacted technical preview below.

Error triggers
TriggerStatusSeverityLeakWhereSnippetResponse preview
malformed_json400nonenone--{"error":{"code":"","message":"Invalid request: Invalid request: invalid character 'n' looking for beginning of object key string (request id: 202607070124481587994998268d9d6PLc1wwzK)","type":"new_api_error"}}
invalid_model503nonenone--{"error":{"code":"model_not_found","message":"No available channel for model nonexistent-xyz-999 under group default (distributor) (request id: 202607070124481938042448268d9d6SJnWG6VS)","type":"new_api_error"}}
wrong_content_type400nonenone--{"error":{"code":"","message":"Model name not specified, model name cannot be empty (request id: 202607070124482149514418268d9d6EwvWvkzC)","type":"new_api_error"}}
missing_messages503nonenone--{"error":{"code":"model_not_found","message":"No available channel for model claude-opus-4-6 under group default (distributor) (request id: 202607070124482361131958268d9d6STpWBs0Y)","type":"new_api_error"}}
unknown_endpoint404nonenone--{"error":{"message":"Invalid URL (POST /v1/nonexistent-route)","type":"invalid_request_error","param":"","code":""}}
force_upstream_error503nonenone--{"error":{"code":"model_not_found","message":"No available channel for model claude-opus-4-6 under group default (distributor) (request id: 202607070124482814235878268d9d6BFGJPA26)","type":"new_api_error"}}
auth_probe401nonenone--{"error":{"code":"","message":"Invalid token (request id: 202607070124483039212988268d9d67MWUGcmr)","type":"new_api_error"}}

Latency variance

Latency variance runtime error

Inconclusive

Inconclusive

Plain-language meaning

Latency variance did not complete, so it cannot prove safety or risk.

Audit evidence

Request timed out after 120000 ms.

How to fix

Inspect gateway and upstream logs, restore the failed route, and rerun only after normal requests succeed consistently.

100

Endpoint profile

Normal

First identifies the network entry, model catalog, gateway fingerprint, and reachability behind this API.

Infrastructure Recon

Endpoint reachability check

Passed

Passed

Plain-language meaning

First checks whether the API accepts requests and returns an explainable response.

Audit evidence

See the structured evidence and redacted technical preview below.

A records

172.67.220.51, 104.21.78.98, 2606:4700:3032::ac43:dc33, 2606:4700:3030::6815:4e62

CNAME

-

NS

-

Entry status

404

WHOIS

whois.iana.org

DNS records
TypeValue
A172.67.220.51 104.21.78.98 2606:4700:3032::ac43:dc33 2606:4700:3030::6815:4e62
CNAME-
NS-
WHOIS lookup
ItemValue
serverwhois.iana.org
summarydomain: TOP; organisation: Hong Kong Zhongze International Limited; organisation: Jiangsu Bangning Science & technology Co.,Ltd.; organisation: Jiangsu Bangning Science & technology Co.,Ltd.
preview% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: TOP organisation: Hong Kong Zhongze International Limited address: UNIT 6, 11/F PROSPERITY PLACE, 6 SHING YIP STREET, KWUN TONG KL address: Hong Kong address: China contact: administrative name: Sven Chen organisation: Jiangsu Bangning Science & technology Co.,Ltd. address: 3th Floor, BangNing Technology Park, 2 YuHua Avenue address: Yuhuatai District address: Nanjing Jiangsu address: China phone: +86 18936016161 fax-no: +86 2586883476 e-mail: [email protected] contact: technical name: YiFeng Shen organisation: Jiangsu Bangning Science & technology Co.,Ltd. address: 3th Floor, BangNing Technology Park, 2 YuHua Avenue address: Yuhuatai District address: Nanjing Jiangsu address: China phone: +86 15895978960 fax-no: +86 02586883476 e-mail: [email protected] nserver: A.ZDNSCLOUD.CN 203.99.24.1 nserver: B.ZDNSCLOUD.CN 203.99.25.1 nserver: C.ZDNSCLOUD.COM 203.99.26.1 nserver: D.ZDNSCLOUD.COM 203.99.27.1 nserver: E.ZDNSCLOUD.CN 203.119.82.1 2401:8d00:15:0:0:0:0:1 nserver: F.ZDNSCLOUD.CN 116.169.54.111 nserver: I.ZDNSCLOUD.CN 2401:8d00:1:0:0:0:0:1 nserver: J.ZDNSCLOUD.COM 2401:8d00:2:0:0:0:0:1 ds-rdata: 26780 8 2 5d6e7869ee8e3b536a617de89482ddd1dcb9db9dbb1ac33d6ed351e2ca095b1b whois: whois.nic.top status: ACTIVE remarks: Registration information: http://www.nic.top created: 201...
HTTP response headers
ItemValue
alt-svch3=":443"; ma=86400
cache-controlmax-age=604800
cache-versionb688f2fb5be447c25e5aa3bd063087a83db32a288bf6a4f35f2d8db310e40b14
cf-cache-statusDYNAMIC
cf-raya172fba36865c74e-LAX
connectionkeep-alive
content-encodinggzip
content-length109
content-typeapplication/json; charset=utf-8
dateTue, 07 Jul 2026 01:12:47 GMT
nel{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=i9CQ7SLPGbfxw6DCkmX%2FSmmqx8SIOfdCRZKeY295K3lmedqIcyUDUjrFC0Kanmkny%2BN76HtrI8wBM1gab584OKImTSbuQv9JQTDgqdk8BCwH1i9WkKaoFA8xnb%2BSqdd4s0Uutw%3D%3D"}]}
servercloudflare
set-cookieserver_name_session=6edcdedafce306fae8e873dcf557ea8d; Max-Age=86400; httponly; path=/
speculation-rules"/cdn-cgi/speculation"
varyAccept-Encoding
x-oneapi-request-id202607070112479228397718268d9d6d1ynmFYw
System identification response
ItemValue
HTTP404
servercloudflare
body preview{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}

Technical details (redacted)

{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}

SSL/TLS

TLS certificate check

Certificate found

Notice

Plain-language meaning

The TLS certificate helps identify the encrypted entry layer, but does not prove model safety.

Audit evidence

See the structured evidence and redacted technical preview below.

A records

172.67.220.51, 104.21.78.98, 2606:4700:3032::ac43:dc33, 2606:4700:3030::6815:4e62

CNAME

-

NS

-

Entry status

404

WHOIS

whois.iana.org

DNS records
TypeValue
A172.67.220.51 104.21.78.98 2606:4700:3032::ac43:dc33 2606:4700:3030::6815:4e62
CNAME-
NS-
WHOIS lookup
ItemValue
serverwhois.iana.org
summarydomain: TOP; organisation: Hong Kong Zhongze International Limited; organisation: Jiangsu Bangning Science & technology Co.,Ltd.; organisation: Jiangsu Bangning Science & technology Co.,Ltd.
preview% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: TOP organisation: Hong Kong Zhongze International Limited address: UNIT 6, 11/F PROSPERITY PLACE, 6 SHING YIP STREET, KWUN TONG KL address: Hong Kong address: China contact: administrative name: Sven Chen organisation: Jiangsu Bangning Science & technology Co.,Ltd. address: 3th Floor, BangNing Technology Park, 2 YuHua Avenue address: Yuhuatai District address: Nanjing Jiangsu address: China phone: +86 18936016161 fax-no: +86 2586883476 e-mail: [email protected] contact: technical name: YiFeng Shen organisation: Jiangsu Bangning Science & technology Co.,Ltd. address: 3th Floor, BangNing Technology Park, 2 YuHua Avenue address: Yuhuatai District address: Nanjing Jiangsu address: China phone: +86 15895978960 fax-no: +86 02586883476 e-mail: [email protected] nserver: A.ZDNSCLOUD.CN 203.99.24.1 nserver: B.ZDNSCLOUD.CN 203.99.25.1 nserver: C.ZDNSCLOUD.COM 203.99.26.1 nserver: D.ZDNSCLOUD.COM 203.99.27.1 nserver: E.ZDNSCLOUD.CN 203.119.82.1 2401:8d00:15:0:0:0:0:1 nserver: F.ZDNSCLOUD.CN 116.169.54.111 nserver: I.ZDNSCLOUD.CN 2401:8d00:1:0:0:0:0:1 nserver: J.ZDNSCLOUD.COM 2401:8d00:2:0:0:0:0:1 ds-rdata: 26780 8 2 5d6e7869ee8e3b536a617de89482ddd1dcb9db9dbb1ac33d6ed351e2ca095b1b whois: whois.nic.top status: ACTIVE remarks: Registration information: http://www.nic.top created: 201...
HTTP response headers
ItemValue
alt-svch3=":443"; ma=86400
cache-controlmax-age=604800
cache-versionb688f2fb5be447c25e5aa3bd063087a83db32a288bf6a4f35f2d8db310e40b14
cf-cache-statusDYNAMIC
cf-raya172fba36865c74e-LAX
connectionkeep-alive
content-encodinggzip
content-length109
content-typeapplication/json; charset=utf-8
dateTue, 07 Jul 2026 01:12:47 GMT
nel{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=i9CQ7SLPGbfxw6DCkmX%2FSmmqx8SIOfdCRZKeY295K3lmedqIcyUDUjrFC0Kanmkny%2BN76HtrI8wBM1gab584OKImTSbuQv9JQTDgqdk8BCwH1i9WkKaoFA8xnb%2BSqdd4s0Uutw%3D%3D"}]}
servercloudflare
set-cookieserver_name_session=6edcdedafce306fae8e873dcf557ea8d; Max-Age=86400; httponly; path=/
speculation-rules"/cdn-cgi/speculation"
varyAccept-Encoding
x-oneapi-request-id202607070112479228397718268d9d6d1ynmFYw
System identification response
ItemValue
HTTP404
servercloudflare
body preview{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}

Technical details (redacted)

{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}

Model List

Model catalog enumeration

Passed

Passed

Plain-language meaning

The model catalog helps verify which models this endpoint claims to support.

Audit evidence

See the structured evidence and redacted technical preview below.

Model count

143

Requested model listed

yes

Model catalog sample
Model
meta/llama-3.1-8b-instruct
nvidia/nemotron-3-nano-30b-a3b
grok-4.3-high
nvidia/riva-translate-4b-instruct
deepseek-reasoner
google/gemma-3-12b-it
upstage/solar-10.7b-instruct
nvidia/llama-3.1-nemotron-nano-vl-8b-v1
gemini-1.5-pro
grok-4.20-0309-non-reasoning
nvidia/nemotron-3.5-content-safety
mistralai/mixtral-8x22b-v0.1
mistralai/mistral-7b-instruct-v0.3
grok-4.20-fast
meta/llama-3.2-11b-vision-instruct
grok-4.20-multi-agent-high
nvidia/nemotron-4-340b-instruct
google/gemma-2b
grok-4.20-multi-agent-medium
mistralai/mistral-small-4-119b-2603

Infrastructure Fingerprint

Infrastructure fingerprint

cloudflare

Notice

Plain-language meaning

Framework fingerprinting identifies the gateway stack; it is informational and helps explain other anomalies.

Audit evidence

HTTP 404; HTTP 200; HTTP 404

Framework

cloudflare

Confidence

confirmed

Fingerprint probes
ProbePathStatusFrameworkserverHeadersSignalsErrorResponse preview
landing/404cloudflarecloudflareserver=cloudflare; cf-ray=a17313167ba4a158-LAXheader:cf-ray:present; header:server~cloudflare-{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}
models/v1/models200cloudflarecloudflareserver=cloudflare; cf-ray=a173131688546cd4-SJCheader:cf-ray:present; header:server~cloudflare-{"data":[{"id":"meta/llama-3.1-8b-instruct","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"nvidia/nemotron-3-nano-30b-a3b","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"grok-4.3-high","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"nvidia/riva-translate-4b-instruct","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"deepseek-reasoner","object":"model","created":1626777600,"owned_by":"deepseek","supported_endpoint_types":["openai"]},{"id":"google/gemma-3-12b-it","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"upstage/solar-10.7b-instruct","object":"model","created":1626777600,"owned_by":"custom","supported_endpoint_types":["openai"]},{"id":"nvidia/llama-3.1-nemotron-nano-vl-8b-v1","object":"model","created":1626...
notfound/nonexistent-abc12345xyz404cloudflarecloudflareserver=cloudflare; cf-ray=a17313168de87af4-SJCheader:cf-ray:present; header:server~cloudflare-{"error":{"message":"Invalid URL (GET /v1/nonexistent-abc12345xyz)","type":"invalid_request_error","param":"","code":""}}

Recommended actions

Rerun first

The evidence is incomplete. Do not treat this as a pass; rerun with enough quota or another model.

More than a speed test: inspect whether the relay path was tampered with

lmspeed puts model identity, prompt leakage, context boundaries, error leakage, and stream integrity into one security comparison table, so you can baseline a relay before wiring it into production.

Dimensionlmspeedhvoy.aicctest.ai
Token injectionCompare actual token usage with the expected countCoveredNot coveredCovered
Prompt extractionProbe hidden system prompt leakageCoveredNot coveredNot covered
Identity substitutionDetect whether Claude is actually answered by another modelCoveredCoveredNot covered
Jailbreak defenseCheck common jailbreak vectorsCoveredNot coveredNot covered
Context truncationFind the real context-window boundaryCoveredNot coveredNot covered
Tool-call rewrite (AC-1.a)Detect rewritten package commands and tool argumentsCoveredNot coveredNot covered
Error response leakage (AC-2)Probe credentials, paths, and internal field leakageCoveredNot coveredNot covered
Stream integrity (SSE)Validate event types, usage, and thinking signaturesCoveredCoveredNot covered
Web3 injectionCheck whether signing context is polluted by the relay layerCoveredNot coveredNot covered
Channel fingerprintProtobuf signatures and multimodal interpretation checksIn designSoonNot coveredCovered
CoveredCoveredNot coveredNot coveredIn designSoonIn design

How the 13-check audit breaks down relay risk

Each check keeps public evidence redacted: you can see where the path looks suspicious without publishing API keys, system prompts, or internal paths.

Threat categories are based on Liu et al., "Your Agent Is Mine" (arXiv:2604.08407)

Check 2

Model list

Read the public model catalog and check whether the requested model is actually listed.

Check 3

Token injection

Compare billed or reported input tokens with the expected count to find a hidden system prompt.

Check 4

Prompt extraction

Try verbatim, translation, and JSON-continuation probes to extract hidden system instructions.

Check 7

Context window

Increase context until the usable boundary appears, not only the advertised window.

Check 8

Tool-call rewrite

Detect whether package-install commands are rewritten on the return path.

Check 10

Stream integrity

Validate SSE event structure and whether the streamed model name matches the request.

Check 13

Latency variance

Repeat the same request and look for queues, extra hops, or silent model switching.

Notes, principles, and references

  1. Core principle: LMSpeed sends controlled probes with known intent, then compares expected behavior with returned text, token usage, stream events, tool-call arguments, and error shape. A mismatch is treated as evidence that the relay path may have rewritten, injected, truncated, or leaked data.
  2. API relay / proxy means a third-party endpoint between you and the upstream model provider. Because it sits in the plaintext path, it can route, inspect, rewrite, or truncate requests and responses before they reach your app.
  3. Token injection means hidden relay-side instructions added before your prompt. The check looks for unexpected prompt-token growth, leaked instruction traces, or behavior that follows a hidden instruction instead of the user request.
  4. Tool-call rewriting / AC-1.a means relay-side response modification such as changing a package-install command, dependency name, or other tool-call argument. The probe uses command-like outputs because a small rewrite there can become a real supply-chain action.
  5. Error response leakage / AC-2 means malformed requests are used to check whether errors expose credentials, environment variables, file paths, framework names, or proxy internals. Clean relays should fail without echoing secrets.
  6. SSE and Web3 checks cover stream event integrity, usage monotonicity, and wallet signature-isolation probes. The idea is to verify that streaming metadata stays coherent and that relay prompts cannot steer signature behavior.
  7. Coverage is informed by the api-relay-audit GitHub repository and the paper Your Agent Is Mine.