registry / Remote code execution / @okx_ai/okx-trade-mcp
@okx_ai/okx-trade-mcp
OKX MCP Server - Model Context Protocol server for OKX exchange
This report shows the evidence for @okx_ai/okx-trade-mcp@1.4.8. 5 of 7 known versions are blocked or flagged. The newest version, 1.4.9, is flagged. See all versions.
AI Security Review
scanned 29d ago · by lpm-firewall-aiThe postinstall hook fetches native binaries from a CDN and makes them executable, using a checksum served by the same host, including static.jingyunyilian.com. The published server then executes those binaries, so install can turn a remote response into local code.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
npm install lifecycle postinstall, then a later run of the MCP server that calls the pilot or auth helper.
Impact
A response from the CDN becomes a user-privileged native executable on the machine without a hash pinned in the published package.
Mechanism
scripts/postinstall.js fetches the platform binary over HTTPS, accepts a checksum.json from the same host, writes it under the user home directory, and marks it executable. dist/index.js then execFile or spawn that path.
Attack narrative
Installing the package runs scripts/postinstall.js. That script downloads okx-pilot and okx-auth into ~/.okx/bin, trying static.jingyunyilian.com before static.okx.com and static.coinall.ltd. The checksum is taken from the same host, so the package does not pin the binary hash. The file is made executable. When the server later needs a pilot route or an auth token, dist/index.js executes that downloaded binary with the user privileges.
AI rationale
The postinstall hook fetches native binaries from a CDN and makes them executable, using a checksum served by the same host, including static.jingyunyilian.com. The published server then executes those binaries, so install can turn a remote response into local code.
Evidence
package.jsonscripts/postinstall.jsdist/index.js~/.okx/bin/okx-pilot~/.okx/bin/okx-auth
Network endpoints6
static.jingyunyilian.com/upgradeapp/tools/pilotstatic.jingyunyilian.com/upgradeapp/tools/oauthstatic.okx.com/upgradeapp/tools/pilot
Decision evidence
public snapshotAI called this Malicious at 90.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json postinstall runs scripts/postinstall.js and ignores a failing exit status.
- The install script downloads okx-pilot and okx-auth into the user home .okx/bin directory from static.jingyunyilian.com, then static.okx.com and static.coinall.ltd.
- The checksum file is fetched from the same CDN host as the binary and is not pinned in the package.
- After that remote checksum matches, non-Windows installs chmod the file 755.
- dist/index.js later execFile-runs okx-pilot and spawn-runs okx-auth.
Evidence against
- A failed download does not fail npm install.
- okx-pilot is only invoked for hostnames matching *.okx.com.
- Writes to Claude, Cursor, Windsurf, and VS Code config happen only from the explicit setup subcommand.
- The package source has no eval, Function, or obfuscated payload.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts changed=test:unit
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js || exit 0
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js || exit 0
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
Findings
2 Critical6 High4 Medium4 Low
CriticalManifest Confusionpackage.json
CriticalPrevious Version Dangerous Deltadist/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/index.js
HighSame File Env Network Executiondist/index.js
HighHost Fingerprint Exfiltrationscripts/postinstall.js
HighKnown Malware Source Similaritydist/index.js
HighKnown Malware Source Fingerprint Signaturedist/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to @okx_ai/okx-trade-mcp@1.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing @okx_ai/okx-trade-mcp@1.4.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.