Sato Hub
Package

dexpaprika-mcp

npm:dexpaprika-mcp · v2.9.3 · sha256:cd49dc0f26f6 · as of 2026-11-09

Does it take your key?
no evidence
No private-key read found in what we read of its setup and published code — the limits say how much that was.
No evidence line on file for this question yet.
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
No action that signs or sends funds found.
No evidence line on file for this question yet.
What changed?
observed
No change in key, host or fund behaviour since 2.9.2.
We ran it with planted test keys and saw it.

Is this your project? Respond →Dispute this reading

Hosts contacted

HostWhenRoleEvidence
api-pro.dexpaprika.comcodevendortraced
api.dexpaprika.comcodevendortraced
console.dexpaprika.comcodevendortraced
dexpaprika.comcodevendortraced
docs.dexpaprika.comcodevendortraced
registry.npmjs.orginstallregistryobserved
Evidence (6 lines)
  • observedO-hosts2026-11-09

    registry.npmjs.org was contacted during install (registry).

    sandbox:obs_6b45e2e78760ddc3

  • tracedT-hosts2026-11-09

    api-pro.dexpaprika.com appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-11-09

    api.dexpaprika.com appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-11-09

    console.dexpaprika.com appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-11-09

    dexpaprika.com appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-11-09

    docs.dexpaprika.com appears in shipped code (vendor).

    dist/index.js

Limits

  • Traced analysis follows flows inside one module and one hop across a relative import; a longer chain 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.
  • 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..

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-3

Maintain this project? Respond to this reading

Loading sign-in…