Sato Hub
← Sato Check

Sato Check · Package

@selfxyz/enterprise-sdk

npm:@selfxyz/enterprise-sdk · v0.4.1 · sha256:4a6bf7208d97 · as of 2026-09-26

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

HostWhenRoleEvidence
edge.dashboard.self.xyzcodevendortraced
verifier.self.xyzcodevendortraced
verifier.staging.self.xyzcodevendortraced
registry.npmjs.orginstallregistryobserved
codeload.github.cominstallregistryobserved
nodejs.orginstallotherobserved
Evidence (6 lines)
  • observedO-hosts2026-09-25

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

    sandbox:obs_e5cd7422422698d2

  • observedO-hosts2026-09-25

    codeload.github.com was contacted during install (registry).

    sandbox:obs_e5cd7422422698d2

  • observedO-hosts2026-09-25

    nodejs.org was contacted during install (other).

    sandbox:obs_e5cd7422422698d2

  • tracedT-hosts2026-09-26

    edge.dashboard.self.xyz appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-09-26

    verifier.self.xyz appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-09-26

    verifier.staging.self.xyz appears in shipped code (vendor).

    dist/index.js

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

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…