The mirror serves a legitimate product sync purpose, but this version’s configuration enables it by default despite comments and documentation saying it should require opt-in. Because it can automatically transfer account data and skill files, this is suspicious rather than clean.
Static reason
No blocking static signals were detected.
Trigger
Service startup when account and console-token wiring is present; sync begins immediately and repeats periodically.
Impact
Product records and skill files may be synchronized automatically to the deployment without the documented opt-in; this is an undisclosed-by-default data transfer, not evidence of credential theft.
Mechanism
Posts the mirror document with a bearer token and account identifier to the configured gateway, defaulting to harness.mwt.one. The runtime check does not require the mirror key mentioned in its warning.
Evidence
cordis.patch.ymlnode_modules/@deepseek-ai/dsh-faberloom-mirror/lib/index.jsnode_modules/@deepseek-ai/dsh-faberloom-mirror/README.md<home>/mirror-status.json$DSH_HOME/skills/<name>/SKILL.md<home>/storages