channel-worker@2.5.115

Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

Channel Manager worker daemon — runs on remote machines to execute video pipeline jobs

AI Security Review

scanned 8d ago · by lpm-firewall-ai

The flagged process execution and dynamic loading support the package's worker and update functions, and the dynamic browser-script loader is constrained to package-local scripts. The automatic self-update is package-aligned behavior; source inspection found no concrete attack behavior.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

An operator pairs or configures the worker and starts the daemon; update checks run while it is active.

Impact

No unauthorized credential transfer, destructive behavior, or other concrete attack impact was established from the inspected source.

Mechanism

The daemon sends token-authenticated requests to its configured API and installs newer releases of this package from npm. Browser automation scripts are resolved from the package scripts directory.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 88.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes a daemon and CLI, defines only start and dev scripts, and has no install lifecycle hook or self-dependency.
The CLI requires a worker token before starting; its self-test loads modules from the local lib directory.
The updater fetches the latest channel-worker version from npm and installs that package; the daemon starts periodic update checks.
Runtime command processing polls the API and dispatches worker tasks.
Playwright script names are validated and resolved to files under the package scripts directory.
API requests attach the worker token to the configured API base URL.

Evidence against

Behavioral surface

Source

ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 30 file(s), 658 KB of source, external domains: 127.0.0.1, affiliate.shopee.vn, api.channel.tunasm.art, down-vn.img.susercontent.com, registry.npmjs.org, shopee.vn, studio.youtube.com, www.facebook.com, www.youtube.com

Source & flagged code

5 flagged

bin/cli.jsView file

182L183: const { spawn } = require('child_process'); L184: const LOG_FILE = path.join(CONFIG_DIR, 'daemon.log');

High

Child Process

Package source references child process execution.

bin/cli.jsView on unpkg · L182

2L3: const fs = require('fs'); L4: const path = require('path');

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/cli.jsView on unpkg · L2

lib/updater.jsView file

29console.log(`[updater] Installing ${PKG_NAME}@${version}...`); L30: execSync(`npm install -g ${PKG_NAME}@${version}`, { stdio: 'inherit', windowsHide: true }); L31: console.log(`[updater] Installed ${PKG_NAME}@${version}`);

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

lib/updater.jsView on unpkg · L29

Findings

1 Critical3 High4 Medium4 Low

CriticalPrevious Version Dangerous Deltalib/command-poller.js

HighChild Processbin/cli.js

HighRuntime Package Installlib/updater.js

HighSemantic Analysis Limitedlib/daemon.js#virtual:normalized:round1

MediumDynamic Requirebin/cli.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to channel-worker@2.5.115.

See all versions of channel-worker for other recorded verdicts.

Review the evidence and your use of channel-worker@2.5.115 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-19 17:49:59.010Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.