T08 · Insecure Dependencies
- Location
SKILL.md:64- Finding
Unpinned Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:64
Vulnerability Type: Supply-chain exposure through unpinned npm dependencies
Risk Level: MediumVulnerable Code
bash npm install @larksuiteoapi/node-sdk axiosTechnical Analysis
The installation command does not specify reviewed package versions. The project also contains no package lockfile or integrity metadata. Consequently, users following the documentation will install whichever package versions the npm registry resolves at that time.
This does not prove that either named package is malicious. However, the mutable dependency resolution makes the effective installed code different from the code reviewed during this audit. A compromised maintainer account, malicious future release, or registry-level package compromise could introduce arbitrary installation or runtime behavior.
Attack Path
- An attacker compromises a referenced package or publishes a malicious version through its release channel.
- A user follows the documented
npm installcommand after that version becomes the default registry resolution. - npm downloads and installs the affected version without comparison against a reviewed lockfile or integrity baseline.
- Malicious lifecycle or runtime code executes with the privileges of the user running npm or the bot process.
- That code may access Feishu credentials, enterprise messages, files, and other resources available to the process.
Impact Assessment
Successful exploitation could provide code execution under the bot's operating-system account. The accessible scope would include environment variables such as
FEISHU_APP_IDandFEISHU_APP_SECRET, local files readable by that account, outbound network access, and enterprise data processed by the integration. Additional impact depends on the host account's privileges and granted Feishu scopes.- Remediation
View remediation
Remediation Suggestions
- Define dependencies in
package.jsonusing exact, reviewed versions rather than unconstrained installation commands. - Commit a generated
package-lock.jsonand instruct users to install withnpm ci. - Review package provenance, release history, lifecycle scripts, and transitive dependencies before pinning versions.
- Use npm integrity verification and automated dependency scanning.
- Run the integration under a dedicated, unprivileged operating-system account.
- Establish a controlled process for reviewing and updating dependency versions.
- Define dependencies in
