--- canonical: "https://firewall.lpm.dev/npm/@tencentcloud/tmeet" markdown: "https://firewall.lpm.dev/npm/@tencentcloud/tmeet/v/1.0.16.md" package: "@tencentcloud/tmeet" report_status: "published" title: "@tencentcloud/tmeet@1.0.16 npm security report" verdict: "suspicious" version: "1.0.16" --- # @tencentcloud/tmeet@1.0.16 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 **Flagged — allowed with a warning** — Allowed by default policy, but 12 finding(s) warrant review before installing. - **Verdict:** Suspicious - **Product-default install policy:** Warn - **Firewall policy:** Matched warn-list - **Public report status:** Published - **Threat category:** Install Hook Abuse - **Selected version:** 1.0.16 - **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: suspicious; recommendation: downgrade to warn. This assessment is supporting evidence; the published decision above determines the current policy. Installing the package executes a bundled native binary without a user command. The visible arguments request logout, but the binary is stripped and cannot be fully audited statically. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Suspicious - **Recorded analysis confidence:** 84.0% - **Started:** 2026-09-13T23:37:37.156Z - **Finished:** 2026-09-13T23:38:34.262Z - **Download time:** 1271 ms - **Static scan time:** 122 ms - **AI review time:** 55712 ms - **Total time:** 57106 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 executes a bundled native binary without a user command. The visible arguments request logout, but the binary is stripped and cannot be fully audited statically. - **Trigger:** npm installation runs postinstall. - **Impact:** It may alter existing tmeet authentication state during installation; unverified native behavior remains an install-time risk. - **Evidence paths:** package.json, scripts/cleanup.js - **Review source:** ai\_review - **Reviewed:** 2026-09-13T23:38:34.262Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** Permission change followed by native binary execution with auth logout arguments. - **Rationale:** The package has a real unconsented install-time native execution path, but the readable code limits its stated action to tmeet logout and does not establish malicious behavior. Treat the opaque lifecycle execution as unresolved risk rather than a confirmed attack. - **Files touched:** scripts/cleanup.js, dist/tmeet-Linux-x86\_64 ### Review decision - **Verdict:** Suspicious - **Confidence:** 84.0% - **Recommended action:** downgrade\_to\_warn - **Intent class:** Dangerous Capability - **False-positive risk:** Medium - **Evidence for warning:** Installation automatically runs a cleanup script., The cleanup script changes a bundled binary's permissions and executes its auth logout command., The invoked executable is a stripped native binary, so its install-time behavior cannot be fully verified from source. - **Evidence against:** The visible lifecycle command is specifically an auth logout action rather than a downloader or shell command., The JavaScript launcher only selects and executes the packaged platform binary., No self-dependency, secret harvesting code, remote payload retrieval, or agent-control configuration write was found in the readable scripts. ## Affected versions and remediation This report applies to @tencentcloud/tmeet@1.0.16. - Review the evidence and your use of @tencentcloud/tmeet@1.0.16 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. ## 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 = 7278776 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:** 97.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 = normalized_sha256 matchedPackage = @tencentcloud/tmeet@1.0.18 matchedPath = scripts/tmeet.js matchedIdentity = npm:QHRlbmNlbnRjbG91ZC90bWVldA:1.0.18 similarity = 1.000 summary = normalized source hash matched finalized malicious source ``` ### 10. High: Known Malware Source Fingerprint Signature - **Category:** Supply Chain - **Confidence:** 94.0% - **Path:** scripts/tmeet.js - **Public source:** [View source]() Source fingerprint signature matches a known malicious package signature; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = malicious_source_fingerprint_signature signature = b9e61f219e29170f signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @tencentcloud/tmeet@1.0.18 matchedPath = scripts/tmeet.js matchedIdentity = npm:QHRlbmNlbnRjbG91ZC90bWVldA:1.0.18 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious ``` ### 11. Medium: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 84.0% - **Path:** package.json - **Public source:** [View source]() Installation automatically runs a cleanup script. Public source snippet (untrusted): ```json "scripts": { "postinstall": "node scripts/cleanup.js" } ``` ### 12. Medium: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 84.0% - **Path:** scripts/cleanup.js - **Public source:** [View source]() The cleanup script changes a bundled binary's permissions and executes its auth logout command. Public source snippet (untrusted): ```javascript // 确保可执行权限（Windows 不需要） if (platform !== "win32") { fs.chmodSync(binaryPath, 0o755); } // 执行 tmeet auth logout 清理登录态 try { execFileSync(binaryPath, ["auth", "logout"], { stdio: "inherit" }); } catch (err) { process.exit(0); } ``` ## 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.16 - **License:** MIT - **Version published:** 2026-09-02T12:38:45.104Z - **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 工具 - **Maintainers:** qingmei\_t, klauslin - **Runtime engines:** node: \>=14 - **Artifact files:** 10 - **Artifact unpacked size:** 36,314,645 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]() - [Repository]() - [Homepage]() - [Issues]()