Sato Check · Package
@dydxprotocol/v4-client-js
npm:@dydxprotocol/v4-client-js · v3.6.0 · sha256:0f4e92033685 · as of 2026-09-26
- Does it take your key? traced
- It asks for a private key or seed phrase in its setup.
- Our static read of the published artifact found it.
- Does your key leave? observed
- Not observed — no planted key left during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- We ran it with planted test keys and saw it.
- Can it move funds on its own? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- What changed? no evidence
- First profile of this subject — nothing to compare yet.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| dydx-ops-rpc.kingnodes.com | code | rpc | traced |
| dydx-rpc.liquify.com | code | rpc | traced |
| dydx-testnet-archive.allthatnode.com | code | other | traced |
| dydx-testnet.nodefleet.org | code | other | traced |
| faucet.v4testnet.dydx.exchange | code | vendor | traced |
| indexer.dydx.trade | code | other | traced |
| indexer.v4staging.dydx.exchange | code | vendor | traced |
| indexer.v4testnet.dydx.exchange | code | vendor | traced |
| indexer.v4testnet2.dydx.exchange | code | vendor | traced |
| rpc.testnet.noble.strange.love | code | rpc | traced |
| test-dydx-rpc.kingnodes.com | code | rpc | traced |
| validator.v4staging.dydx.exchange | code | vendor | traced |
| validator.v4testnet1.dydx.exchange | code | vendor | traced |
| registry.npmjs.org | install | registry | observed |
Evidence (16 lines)
- observedO-hosts2026-09-25
registry.npmjs.org was contacted during install (registry).
sandbox:obs_5f705c42e989eb4a
- tracedT-hosts2026-09-26
dydx-ops-rpc.kingnodes.com appears in shipped code (rpc).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
dydx-rpc.liquify.com appears in shipped code (rpc).
build/cjs/examples/native_examples.js
- tracedT-hosts2026-09-26
dydx-testnet-archive.allthatnode.com appears in shipped code (other).
build/cjs/examples/optimal_node.js
- tracedT-hosts2026-09-26
dydx-testnet.nodefleet.org appears in shipped code (other).
build/cjs/examples/native_examples.js
- tracedT-hosts2026-09-26
faucet.v4testnet.dydx.exchange appears in shipped code (vendor).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
indexer.dydx.trade appears in shipped code (other).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
indexer.v4staging.dydx.exchange appears in shipped code (vendor).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
indexer.v4testnet.dydx.exchange appears in shipped code (vendor).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
indexer.v4testnet2.dydx.exchange appears in shipped code (vendor).
build/cjs/examples/optimal_node.js
- tracedT-hosts2026-09-26
rpc.testnet.noble.strange.love appears in shipped code (rpc).
build/cjs/examples/noble_example.js
- tracedT-hosts2026-09-26
test-dydx-rpc.kingnodes.com appears in shipped code (rpc).
build/cjs/examples/native_examples.js
- tracedT-hosts2026-09-26
validator.v4staging.dydx.exchange appears in shipped code (vendor).
build/cjs/src/clients/constants.js
- tracedT-hosts2026-09-26
validator.v4testnet1.dydx.exchange appears in shipped code (vendor).
build/cjs/examples/optimal_node.js
- tracedT-key-handling2026-09-26
Turns key material it is GIVEN into an account or signer (mnemonicToSeedSync()); no read of a key from the environment or a key file was found. A signing library does this.
build/esm/src/lib/onboarding.js:58
- declaredD-env-key2026-09-26
Setup names DYDX_TEST_MNEMONIC as something to provide.
@dydxprotocol/v4-client-js@3.6.0/README.md
Limits
- Traced analysis follows flows inside one module only; a key handed from one module to another is not followed.
- Key egress not observed during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- No tool inventory was available, so fund actions were not read.
- Sandbox: DNS queries made directly by the target are not logged; hosts are recorded from proxied HTTP(S) requests and CONNECTs..
- Sandbox: Code that ignores HTTP(S)_PROXY has no route out of the sandbox, so its attempts are not captured..
- Traced: 959 code files; parsed 400, entry points first; __native__/__ios__/v4-native-client.js skipped (over 2 MB).
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
sato.custody/v1 · custody-1
Maintain this project? Respond to this reading
Loading sign-in…