Back to skill

Security audit

电商 Listing 生成器

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed cloud listing generator that uses a Yufluent API key and sends product inputs to Yufluent, with dependency and packaging hygiene notes but no evidence of malicious behavior.

Install only if you are comfortable providing a Yufluent TOKENAPI_KEY and sending product/listing inputs to the Yufluent service. Review TOKENAPI_BASE_URL before use, prefer a pinned or constrained requests version, and verify the packaged cloud client in controlled deployments because yufluent_api.py was not included in the inspected source artifact.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Unpinned Dependencies

Low
Category
Supply Chain
Content
-e ../../packages/tokenapi-sdk
-e ../../packages/tokenapi-harness
requests>=2.31.0
Confidence
95% confidence
Finding
The dependency specification uses a lower-bound constraint (`requests>=2.31.0`) instead of a pinned version, which makes builds non-reproducible and can introduce unexpected or insecure versions over time. In a development requirements file this is less severe than in production, but it still increases supply-chain risk and complicates vulnerability management.

Unpinned Dependencies

Low
Category
Supply Chain
Content
requests>=2.31.0
Confidence
97% confidence
Finding
The dependency is specified as `requests>=2.31.0`, which is not fully pinned and allows installation of different versions over time. This weakens build reproducibility and can unintentionally admit a vulnerable or breaking release through the normal dependency resolution process.

Known Vulnerable Dependency: requests==2.31.0 — 6 advisory(ies): 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); CVE-2026-25645 (Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility func) +3 more

Medium
Category
Supply Chain
Confidence
76% confidence
Finding
Although the file does not explicitly pin `requests==2.31.0`, the allowed range includes 2.31.0, a version with multiple published advisories. That means dependency resolution may install a known vulnerable release, especially in unconstrained or older environments, creating real risk if the affected code paths are exercised.

Known Vulnerable Dependency: requests==2.31.0 — 6 advisory(ies): 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); CVE-2026-25645 (Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility func) +3 more

Medium
Category
Supply Chain
Confidence
92% confidence
Finding
Although the file does not strictly pin `requests==2.31.0`, the specifier `requests>=2.31.0` still permits installation of version 2.31.0, which is flagged with multiple advisories. That means vulnerable versions remain allowed by the dependency policy unless a higher safe lower bound or explicit exclusion is added.

Static analysis

No suspicious patterns detected.