--- canonical: "https://firewall.lpm.dev/npm/@tencentcloud/tmeet/v/1.0.17" markdown: "https://firewall.lpm.dev/npm/@tencentcloud/tmeet/v/1.0.17.md" package: "@tencentcloud/tmeet" report_status: "published" title: "@tencentcloud/tmeet@1.0.17 npm security report" verdict: "malicious" version: "1.0.17" --- # @tencentcloud/tmeet@1.0.17 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Blocked & quarantined** — Existing Tencent Meeting CLI authentication can be removed during package installation. - **Verdict:** Malicious - **Product-default install policy:** Block - **Firewall policy:** Matched malicious - **Public report status:** Published - **Threat category:** Destructive Action - **Selected version:** 1.0.17 - **Selected version is latest:** No - **Analysis source:** AI Security Review (lpm-firewall-ai) This is the current Firewall decision for the selected package version, based on the available public evidence. Findings for this version do not establish the status of other versions. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. Installing the package automatically executes a bundled native program and logs the user out of Tencent Meeting. This is an unconsented destructive change to the package's authentication state. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 96.0% - **Started:** 2026-09-09T11:59:31.085Z - **Finished:** 2026-09-09T12:00:30.007Z - **Download time:** 757 ms - **Static scan time:** 158 ms - **AI review time:** 58004 ms - **Total time:** 58922 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** Installing the package automatically executes a bundled native program and logs the user out of Tencent Meeting. This is an unconsented destructive change to the package's authentication state. - **Trigger:** npm installation, through the postinstall lifecycle hook. - **Impact:** Existing Tencent Meeting CLI authentication can be removed during package installation. - **Evidence paths:** package.json, scripts/cleanup.js, scripts/tmeet.js - **Review source:** ai\_review - **Reviewed:** 2026-09-09T12:00:30.007Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** Postinstall chmods and runs a platform native binary with auth logout. - **Attack narrative:** On npm installation, package.json invokes scripts/cleanup.js. The script selects the current platform binary, sets executable permissions, and runs it with auth logout. This performs an unrequested authentication-state cleanup during installation rather than after an explicit user command. The invoked payload is a bundled native executable, limiting source-level verification of its complete behavior. - **Rationale:** The automatic lifecycle hook performs a concrete destructive action by logging out the user and executes opaque native code. Although the binary appears aligned with a Tencent Meeting CLI, that does not justify unconsented logout during installation. - **Files touched:** scripts/cleanup.js, dist/tmeet-macOS-Intel, dist/tmeet-macOS-AppleSilicon, dist/tmeet-Linux-x86\_64, dist/tmeet-Linux-ARM64, dist/tmeet-Windows-x86\_64.exe ### Review decision - **Verdict:** Malicious - **Confidence:** 96.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **Evidence for block:** The postinstall hook automatically runs scripts/cleanup.js., That script changes a bundled binary's permissions and launches it with auth logout during installation., The command launcher executes platform-specific native binaries, so install-time binary behavior is not auditable from the JavaScript source. - **Evidence against:** The native binary strings describe Tencent Meeting CLI commands, authentication, and Tencent Meeting service endpoints., No JavaScript source evidence shows credential exfiltration, remote payload download, or broad project or agent configuration changes. ## Affected versions and remediation This report applies to @tencentcloud/tmeet@1.0.17. - Avoid installing @tencentcloud/tmeet@1.0.17. Remove it from direct dependencies and check your lockfile for transitive copies. - Choose an independently verified alternative or release. This report does not establish that other versions are safe. - If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment. ## Public findings ### 1. High: Install Time Lifecycle Scripts - **Category:** Manifest - **Confidence:** 90.0% - **Path:** package.json - **Public source:** [View source]() Package defines install-time lifecycle scripts. Public source snippet (untrusted): ```json scripts.postinstall = node scripts/cleanup.js ``` ### 2. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 3. Low: Filesystem - **Category:** Source - **Confidence:** 70.0% Package source references filesystem APIs. ### 4. High: Sandbox Evasion Gated Capability - **Category:** Source - **Confidence:** 84.0% - **Path:** scripts/tmeet.js - **Public source:** [View source]() Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks. Public source snippet (untrusted): ```javascript L7: if (nodeMajor < 14) { L8: var _platform = process.platform; L9: var upgradeHint = ""; ... L12: " # 推荐使用 nvm（Node 版本管理器）：\n" + L13: " curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash\n" + L14: " nvm install 18\n" + ... L34: L35: const { execFileSync } = require("child_process"); L36: const path = require("path"); ... L60: L61: const binaryPath = path.join(__dirname, "..", "dist", binaryName); L62: ``` ### 5. Low: High Entropy Strings - **Category:** Supply Chain - **Confidence:** 55.0% Package source contains high-entropy string patterns. ### 6. Low: Url Strings - **Category:** Supply Chain - **Confidence:** 65.0% Package source contains URL literals. ### 7. Medium: Ships Native Binary - **Category:** Artifact Inventory - **Confidence:** 75.0% - **Path:** dist/tmeet-Linux-x86\_64 - **Public source:** [View source]() Package ships native binary artifacts. Public source snippet (untrusted): ```text path = dist/tmeet-Linux-x86_64 kind = native_binary sizeBytes = 7286968 magicHex = [redacted] ``` ### 8. Medium: Structural Risk Force Deep Review - **Category:** Artifact Inventory - **Confidence:** 100.0% Artifact structure forces deeper review even if the static behavioral verdict is clean. ### 9. High: Known Malware Source Similarity - **Category:** Static - **Confidence:** 95.0% - **Path:** scripts/tmeet.js - **Public source:** [View source]() Source file is highly similar to a previously finalized malicious package; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = token_shingles matchedPackage = @ohos-ports/tencentcloud-tmeet@1.0.16-beta.0 matchedPath = scripts/tmeet.js matchedIdentity = npm:[redacted]:1.0.16-beta.0 similarity = 1.000 shingleOverlap = 48 summary = source token shingles overlapped finalized malicious source ``` ### 10. High: Suspicious Lifecycle Evidence - **Category:** Manifest - **Confidence:** 96.0% - **Path:** package.json - **Public source:** [View source]() The postinstall hook automatically runs scripts/cleanup.js. Public source snippet (untrusted): ```json "scripts": { "postinstall": "node scripts/cleanup.js" } ``` ### 11. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 96.0% - **Path:** scripts/cleanup.js - **Public source:** [View source]() That script changes a bundled binary's permissions and launches it with auth logout during installation. Public source snippet (untrusted): ```javascript // 确保可执行权限（Windows 不需要） if (platform !== "win32") { fs.chmodSync(binaryPath, 0o755); } // 执行 tmeet auth logout 清理登录态 try { execFileSync(binaryPath, ["auth", "logout"], { stdio: "inherit" }); ``` ### 12. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 96.0% - **Path:** scripts/tmeet.js - **Public source:** [View source]() The command launcher executes platform-specific native binaries, so install-time binary behavior is not auditable from the JavaScript source. Public source snippet (untrusted): ```javascript let execPath; try { execPath = ensureExecutable(binaryPath); } catch (err) { console.error(`[tmeet] 无法准备可执行文件: ${err.message}`); console.error(`可能原因：当前环境同时禁止修改文件权限和写入临时目录（${os.tmpdir()}）`); process.exit(1); } // 透传所有参数并继承 stdio，保持与直接调用二进制完全一致的体验 try { execFileSync(execPath, process.argv.slice(2), { stdio: "inherit" }); } ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** Yes - **Published lifecycle scripts:** postinstall - **Dependencies:** 0 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 0 ## Package metadata - **Package:** @tencentcloud/tmeet - **Ecosystem:** npm - **Version:** 1.0.17 - **License:** MIT - **Version published:** 2026-09-09T11:54:10.469Z - **Package first seen:** 2026-07-20T12:24:15.943Z - **Package last seen:** 2026-09-13T23:38:34.262Z - **Known versions:** 5 - **Latest version:** 1.0.18 - **Appeal under review:** No - **Description:** 腾讯会议 CLI 工具 - **Runtime engines:** node: \>=14 - **Artifact files:** 10 - **Artifact unpacked size:** 36,350,842 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]() - [Repository]() - [Homepage]() - [Issues]()