A deep API relay audit for 9527 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: Jun 12, 2026, 1:51 PM
Duration: 1294.9s
Target: 9527code.com
Provider: 9527 API
Model: DeepSeek V4 Pro
Auditor: lmspeed.net

Check health scores

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

Model authenticity

Prompt and instruction

Response integrity and stability

Endpoint profile

Model authenticity

Needs review

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

Instruction conflict

Instruction conflict runtime error

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

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 (AC-1 SSE-level)

SSE event integrity

Inconclusive

Retest

Plain-language meaning

Checks streaming event shape, monotonic usage counters, and model-family consistency.

Audit evidence

No SSE data events were received

How to fix

Preserve SSE event order, IDs, model names, and usage values; disable proxy buffering or transformation and retest disconnect handling.

Event count

Stream model

Usage monotonic

Model compatible

Signature valid

Stream integrity checks

Check	Result
transport	pass
event_shape	weak
usage_monotonic	-
usage_consistent	-
signature_valid	-
stream_model	-
total_events_seen	0
findings	No SSE data events were received

Technical details (redacted)

: PING

: PING

: PING

: PING

: PING

{"error":{"message":"openai_error","type":"bad_response_status_code","param":"","code":"bad_response_status_code"}}

Prompt and instruction

Inconclusive

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

Token injection

Token injection runtime error

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

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

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

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.

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

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

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

Trigger	Status	Severity	Leak	Where	Snippet	Response preview
malformed_json	400	none	none	-	-	{"error":{"code":"","message":"Invalid request: Invalid request: invalid JSON request body (request id: 202606121342191868239518268d9d68vR9a3m3)","type":"new_api_error"}}
invalid_model	503	none	none	-	-	{"error":{"code":"model_not_found","message":"No available channel for model nonexistent-xyz-999 under group free (distributor) (request id: 202606121342193928384898268d9d6zHB4yoWP)","type":"new_api_error"}}
wrong_content_type	400	none	none	-	-	{"error":{"code":"","message":"Model name not specified, model name cannot be empty (request id: 202606121342195904226508268d9d6lk80NxmJ)","type":"new_api_error"}}
missing_messages	503	none	none	-	-	{"error":{"code":"model_not_found","message":"No available channel for model claude-opus-4-6 under group free (distributor) (request id: 202606121342197668277528268d9d6K77du74j)","type":"new_api_error"}}
unknown_endpoint	404	none	none	-	-	{"error":{"message":"Invalid URL (POST /v1/nonexistent-route)","type":"invalid_request_error","param":"","code":""}}
force_upstream_error	503	none	none	-	-	{"error":{"code":"model_not_found","message":"No available channel for model claude-opus-4-6 under group free (distributor) (request id: 202606121342201358985678268d9d6wh7M1LKA)","type":"new_api_error"}}
auth_probe	401	none	none	-	-	{"error":{"code":"","message":"Invalid token (request id: 202606121342203086344308268d9d6A1XfHkwQ)","type":"new_api_error"}}

Latency variance

Latency variance runtime error

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.

Endpoint profile

Inconclusive

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

Infrastructure Recon

Endpoint reachability check

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.179.240, 104.21.31.202, 2606:4700:3030::ac43:b3f0, 2606:4700:3031::6815:1fca

CNAME

anna.ns.cloudflare.com, jacob.ns.cloudflare.com

Entry status

404

WHOIS

未获取

DNS records

Type	Value
A	172.67.179.240 104.21.31.202 2606:4700:3030::ac43:b3f0 2606:4700:3031::6815:1fca
CNAME	-
NS	anna.ns.cloudflare.com jacob.ns.cloudflare.com

WHOIS lookup

Item	Value
server	-
summary	未获取
preview	-

HTTP response headers

Item	Value
alt-svc	h3=":443"; ma=86400
cache-control	max-age=604800
cache-version	b688f2fb5be447c25e5aa3bd063087a83db32a288bf6a4f35f2d8db310e40b14
cf-cache-status	DYNAMIC
cf-ray	a0a935462bb204ec-HKG
connection	keep-alive
content-encoding	br
content-type	application/json; charset=utf-8
date	Fri, 12 Jun 2026 13:30:05 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=m3L0kWhBskJKFyEcErYMGB2WCQc08rGwKo7DtqYoX8%2Btqr8oqQqAnB2MXt%2FgZfxpjCVL6kwq2v%2FacXCsw9wb0JD9EgIPO%2FAPGTOYD0R4kmCuUwqoPPPV%2FZFKGJT10T0%3D"}]}
server	cloudflare
transfer-encoding	chunked
x-new-api-version	0.10.x-9527.fd0ebd65
x-oneapi-request-id	202606120058362762984518268d9d6jrCsz9x2

System identification response

Item	Value
HTTP	404
server	cloudflare
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

Not retrieved

Inconclusive

Plain-language meaning

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

Audit evidence

Certificate details could not be read.

How to fix

Renew the certificate for the correct hostname, serve the full chain, and remove any HTTPS-to-HTTP downgrade before rerunning.

A records

172.67.179.240, 104.21.31.202, 2606:4700:3030::ac43:b3f0, 2606:4700:3031::6815:1fca

CNAME

anna.ns.cloudflare.com, jacob.ns.cloudflare.com

Entry status

404

WHOIS

未获取

DNS records

Type	Value
A	172.67.179.240 104.21.31.202 2606:4700:3030::ac43:b3f0 2606:4700:3031::6815:1fca
CNAME	-
NS	anna.ns.cloudflare.com jacob.ns.cloudflare.com

WHOIS lookup

Item	Value
server	-
summary	未获取
preview	-

HTTP response headers

Item	Value
alt-svc	h3=":443"; ma=86400
cache-control	max-age=604800
cache-version	b688f2fb5be447c25e5aa3bd063087a83db32a288bf6a4f35f2d8db310e40b14
cf-cache-status	DYNAMIC
cf-ray	a0a935462bb204ec-HKG
connection	keep-alive
content-encoding	br
content-type	application/json; charset=utf-8
date	Fri, 12 Jun 2026 13:30:05 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=m3L0kWhBskJKFyEcErYMGB2WCQc08rGwKo7DtqYoX8%2Btqr8oqQqAnB2MXt%2FgZfxpjCVL6kwq2v%2FacXCsw9wb0JD9EgIPO%2FAPGTOYD0R4kmCuUwqoPPPV%2FZFKGJT10T0%3D"}]}
server	cloudflare
transfer-encoding	chunked
x-new-api-version	0.10.x-9527.fd0ebd65
x-oneapi-request-id	202606120058362762984518268d9d6jrCsz9x2

System identification response

Item	Value
HTTP	404
server	cloudflare
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

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

119

Requested model listed

yes

Model catalog sample

Model
01-ai/yi-large
abacusai/dracarys-llama-3.1-70b-instruct
baai/bge-m3
bytedance/seed-oss-36b-instruct
deepseek-ai/deepseek-v4-flash
deepseek-ai/deepseek-v4-pro
deepseek-v4-flash
deepseek-v4-pro
glm-5.1
google/codegemma-1.1-7b
google/codegemma-7b
google/deplot
google/gemma-2-2b-it
google/gemma-2b
google/gemma-3-12b-it
google/gemma-3-27b-it
google/gemma-3-4b-it
google/gemma-3n-e2b-it
google/gemma-3n-e4b-it
google/gemma-4-31b-it

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

Probe	Path	Status	Framework	server	Headers	Signals	Error	Response preview
landing	/	404	cloudflare	cloudflare	server=cloudflare; cf-ray=a0a9519a8bcc1c66-HKG	header:cf-ray:present; header:server~cloudflare	-	{"error":{"message":"Invalid URL (GET /v1)","type":"invalid_request_error","param":"","code":""}}
models	/v1/models	200	cloudflare	cloudflare	server=cloudflare; cf-ray=a0a951995d181f94-HKG	header:cf-ray:present; header:server~cloudflare	-	{"data":[{"id":"01-ai/yi-large","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"abacusai/dracarys-llama-3.1-70b-instruct","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"baai/bge-m3","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"bytedance/seed-oss-36b-instruct","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"deepseek-ai/deepseek-v4-flash","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"deepseek-ai/deepseek-v4-pro","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"deepseek-v4-flash","object":"model","created":1626777600,"owned_by":"openai","supported_endpoint_types":["openai"]},{"id":"deepseek-v4-pro","object":"model","created":1626777600,"owned_by":"openai...
notfound	/nonexistent-abc12345xyz	404	cloudflare	cloudflare	server=cloudflare; cf-ray=a0a951996a65f866-HKG	header:cf-ray:present; header:server~cloudflare	-	{"error":{"message":"Invalid URL (GET /v1/nonexistent-abc12345xyz)","type":"invalid_request_error","param":"","code":""}}

Recommended actions

Use for low-risk tasks, verify critical work

Model authenticity has caution signals. Basic chat may be fine, but verify important output elsewhere.

View audit notes

Findings

SSE event integrity

Caution

Checks streaming event shape, monotonic usage counters, and model-family consistency.

Evidence summary

stream_integrity

Stream integrity

Stream integrity needs review.

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.

Dimension	lmspeed	hvoy.ai	cctest.ai
Token injectionCompare actual token usage with the expected count	Covered	Not covered	Covered
Prompt extractionProbe hidden system prompt leakage	Covered	Not covered	Not covered
Identity substitutionDetect whether Claude is actually answered by another model	Covered	Covered	Not covered
Jailbreak defenseCheck common jailbreak vectors	Covered	Not covered	Not covered
Context truncationFind the real context-window boundary	Covered	Not covered	Not covered
Tool-call rewrite (AC-1.a)Detect rewritten package commands and tool arguments	Covered	Not covered	Not covered
Error response leakage (AC-2)Probe credentials, paths, and internal field leakage	Covered	Not covered	Not covered
Stream integrity (SSE)Validate event types, usage, and thinking signatures	Covered	Covered	Not covered
Web3 injectionCheck whether signing context is polluted by the relay layer	Covered	Not covered	Not covered
Channel fingerprintProtobuf signatures and multimodal interpretation checks	In designSoon	Not covered	Covered

CoveredNot coveredSoonIn 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 1

Notes, principles, and references

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.
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.
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.
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.
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.
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.
Coverage is informed by the api-relay-audit GitHub repository and the paper Your Agent Is Mine.