Back to skill

Security audit

Feishu News

Security checks for vulnerabilities and agentic risk

Overview

The skill is a simple Feishu news helper with no hidden persistence or data access, though its dependencies are unpinned and broader than the mock code currently uses.

Install only in a normal least-privileged environment. Before production use, pin or lock dependencies, remove unused packages while the skill remains mock-only, and clarify whether generic news requests should invoke Feishu specifically.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
requirements.txt:4
Finding

Unpinned and Unused Third-Party Dependencies Increase Supply-Chain Exposure

Content
View full analysis

Vulnerability Details

File Location: requirements.txt:4-11
Vulnerability Type: Unrestricted third-party dependency versions and unnecessary dependencies
Risk Level: Medium

Vulnerable Code:

text
feishu-sdk>=1.0.0

# For web fetching and parsing
requests>=2.25.1
beautifulsoup4>=4.9.3

# For data processing
pandas>=1.2.0

Technical Analysis

The dependency manifest specifies only minimum versions and does not impose upper bounds, exact version pins, lockfile constraints, or package hashes. A package installer can therefore resolve any later compatible release, including versions that have not been reviewed with this project.

None of these packages is imported or used by the supplied Python implementation. The current implementation returns hard-coded mock data and performs no Feishu API requests, web parsing, HTTP requests, or Pandas-based processing. Installing these dependencies consequently introduces avoidable direct and transitive supply-chain exposure without supporting implemented functionality.

This finding does not establish that any listed package is currently malicious. The risk arises because an affected or compromised future package release, dependency substitution, compromised package index, or malicious transitive dependency could be selected during installation. Python package installation may execute build backend or installation-related code in the installer’s security context.

Attack Path

  1. A user or automated deployment system installs the project dependencies using requirements.txt.
  2. The package resolver selects versions newer than the stated minimums because no exact versions or integrity hashes are enforced.
  3. A selected direct or transitive package release has been compromised, substituted, or contains malicious build/install behavior.
  4. The package manager downloads and processes the untrusted release.
  5. Malicious build or installation code execute ...[truncated 945 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove feishu-sdk, requests, beautifulsoup4, and pandas while the project remains a mock implementation and does not import them.
  2. When real integration is implemented, add only dependencies required by reachable production code.
  3. Pin each direct dependency to an exact, reviewed version rather than using unrestricted minimum-version constraints.
  4. Generate and commit a lockfile that fixes transitive dependency versions.
  5. Enforce package integrity using trusted hashes, such as a hash-locked requirements file installed with pip --require-hashes.
  6. Verify package names and publishers against authoritative project documentation before adoption.
  7. Use a trusted package index and prevent unintended fallback to untrusted or private indexes.
  8. Run dependency installation in an isolated, least-privileged build environment without unnecessary credentials or host filesystem access.
  9. Add automated vulnerability and dependency-change monitoring, and require review before lockfile updates are merged.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (7)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The usage examples are generic phrases such as requesting latest or recent news, which can easily overlap with normal conversation and cause the skill to activate when the user is not explicitly invoking this capability. In a news-fetching skill, over-broad triggers are risky because they may pull external content into a conversation unexpectedly, affecting response routing, privacy, or content trust boundaries.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
96% confidence
Finding

The dependency is specified with only a lower bound, so builds may resolve to different versions over time and can silently pull in a vulnerable or incompatible release. This weakens reproducibility and makes it difficult to verify whether deployed environments are using a secure version.

Content

Scanner excerpt · requirements.txt (reported line 4)May include surrounding context.

text
# Feishu News Skill Requirements

# Base dependencies for Feishu integration
feishu-sdk>=1.0.0

# For web fetching and parsing
requests>=2.25.1

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
99% confidence
Finding

requests is unpinned, which allows installation of any future version satisfying the minimum constraint and prevents deterministic, auditable builds. Because requests has multiple historical advisories, the lack of pinning increases the chance of deploying an affected release or introducing breaking security behavior during installs.

Content

Scanner excerpt · requirements.txt (reported line 7)May include surrounding context.

text
feishu-sdk>=1.0.0

# For web fetching and parsing
requests>=2.25.1
beautifulsoup4>=4.9.3

# For data processing

Unverifiable Dependency: requests has 16 known advisory(ies) (CVE-2014-1830 (Exposure of Sensitive Information to an Unauthorized Actor in Requests); CVE-2024-47081 (Requests vulnerable to .netrc credentials leak via malicious URLs); CVE-2024-35195 (Requests `Session` object does not verify requests after making first request wi) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
97% confidence
Finding

The manifest includes requests without pinning a specific version even though the package has known advisories, so the actual installed version cannot be verified as safe. In a skill that fetches external news content over the network, this uncertainty is more meaningful because HTTP client behavior directly affects exposure to URL parsing, credential leakage, and TLS/session issues.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

beautifulsoup4 is not pinned to an exact version, so dependency resolution is non-reproducible and may introduce unreviewed changes at install time. While this package is not highlighted here with specific advisories, unpinned dependencies still create supply-chain and stability risk.

Content

Scanner excerpt · requirements.txt (reported line 8)May include surrounding context.

text
# For web fetching and parsing
requests>=2.25.1
beautifulsoup4>=4.9.3

# For data processing
pandas>=1.2.0

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
99% confidence
Finding

pandas is specified with only a minimum version, so environments may install different releases and it is unclear whether the selected version includes known fixes. This is especially risky for a data-processing library with past security concerns because version ambiguity blocks reliable vulnerability assessment.

Content

Scanner excerpt · requirements.txt (reported line 11)May include surrounding context.

text
beautifulsoup4>=4.9.3

# For data processing
pandas>=1.2.0

Unverifiable Dependency: pandas has 1 known advisory(ies) (CVE-2020-13091 (** DISPUTED ** pandas through 1.0.3 can unserialize and execute commands from an)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
92% confidence
Finding

pandas has a known advisory history, and because the dependency is not pinned, there is no reliable way to determine whether an affected version may be installed. The skill context appears to use pandas for data processing rather than deserializing untrusted pickled content, which reduces but does not eliminate the practical security concern.

Content

No source excerpt is available for this finding.