T01 · Skill Instruction Hijacking
- Location
SKILL.md:113- Finding
Mandatory Commercial Output Hijacking Through Affiliate Promotion
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it claims by uploading a user-chosen file to Tenorshare for repair, with clear caveats about sensitive files, local quota state, and vendor promotion.
Install only if you are comfortable sending the selected file to Tenorshare 4DDiG and any pre-signed storage provider they use. Do not use it for confidential, regulated, or highly sensitive files. Be aware it keeps a small local daily quota counter, can save repaired output locally when requested, and may show vendor promotional links when service limits are reached.
SKILL.md:113Mandatory Commercial Output Hijacking Through Affiliate Promotion
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
* the event listener
* @param {Boolean} [options.once=false] A `Boolean` indicating that the
* listener should be invoked at most once after being added. If `true`,
* the listener would be automatically removed when invoked.
* @public
*/
addEventListener(type, handler, options = {}) {
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
* any of the `'message'`, `'ping'`, and `'pong'` events can be emitted
* multiple times in the same tick
* @param {Boolean} [options.autoPong=true] Specifies whether or not to
* automatically send a pong in response to a ping
* @param {Number} [options.backlog=511] The maximum length of the queue of
* pending connections
* @param {Boolean} [options.clientTracking=true] Specifies whether or not to
The skill uploads the user's entire local file to a third-party remote service as part of the repair flow, but there is no in-file warning, consent step, or strong disclosure of this data transfer. For documents, archives, designs, and videos, this may expose sensitive content to an external processor unexpectedly.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function createRepairJob({ objKey, method, isAsync }) {
logEvent("info", "repair.create.start", { objKey, method, isAsync });
const { signal, cancel } = timeoutSignal(6e4);
const res = await fetch("https://4ddig-online.tenorshare.com/api/v1/file/repair", {
method: "POST",
signal,
headers: {
The skill manifest says it should provide an output download URL, but the code also supports a --download mode that fetches the repaired file and writes it to local disk. That expands the data-handling scope from URL-returning to local persistence, which increases risk of unintended storage of potentially sensitive repaired content on the host.
Although the manifest frames the skill as returning a download URL, the implementation writes persistent operational state to disk via limit.json. This creates a mismatch between declared behavior and actual side effects, reducing transparency and potentially violating least-surprise and least-persistence expectations.
The code persists a hidden daily usage counter in limit.json under the executable directory, which is unrelated to the stated file-repair/output-URL purpose. Undeclared local state can surprise operators, affect reproducibility, and create an unauthorized control mechanism over future executions.
The esbuild dependency is specified with a caret range, which allows different versions to be installed over time. That weakens build reproducibility and makes it harder to verify whether the installed version includes known security fixes or vulnerable behavior, especially in a supply-chain context.
"build:repair": "esbuild scripts/repair-video.js --bundle --platform=node --format=cjs --target=node18 --outfile=dist/repair-file.bundle.cjs"
},
"devDependencies": {
"esbuild": "^0.20.2"
},
"dependencies": {
"mime-types": "^2.1.35",
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
The mime-types package is not pinned to an exact version, so installs may resolve to different releases over time. While not dangerous by itself, this increases supply-chain uncertainty and can introduce unexpected vulnerable or incompatible dependency versions into the skill.
"esbuild": "^0.20.2"
},
"dependencies": {
"mime-types": "^2.1.35",
"ws": "^8.17.0"
}
}
The ws package is unpinned and has a history of security advisories, so allowing semver drift makes it unclear which code will actually be deployed. In a file-repair skill that may expose network-facing functionality, uncertainty around the exact ws version increases the risk of inheriting denial-of-service or information disclosure flaws.
},
"dependencies": {
"mime-types": "^2.1.35",
"ws": "^8.17.0"
}
}
The manifest references ws with a non-exact version, and ws has multiple published advisories. Because the installed version cannot be determined from this file alone, the project may resolve to a vulnerable release, which is more concerning here because a file-repair service may accept untrusted client input over network channels.
No suspicious patterns detected.