T07 · Tool Hijacking and Spoofing
- Location
auto_agent_4974.py:6- Finding
Untrusted Import Path Enables Local Module Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be a Bilibili learning/knowledge-entry helper, but it relies on an unreviewed external Python module path and can persist caller-supplied text into a knowledge base.
Review before installing. Use it only in an environment where D:\\coze-local\\db and learn.py are trusted and protected from modification, and expect the skill to write entries into a local knowledge base when invoked. Avoid broad automatic activation on the word "agent" unless you are comfortable with accidental knowledge writes.
auto_agent_4974.py:6Untrusted Import Path Enables Local Module Hijacking
auto_agent_4974.py:12Unvalidated User Input Is Written to Persistent Agent Knowledge
The trigger phrase 'agent' is extremely broad and is likely to activate during normal conversation unrelated to this skill. That can cause unintended invocation, context hijacking, or accidental execution of skill behavior when the user did not explicitly request it, which is a real security and safety issue for agent systems.
The skill's visible title, functionality description, and trigger text are entirely in Chinese, with no indication that users may interact in other languages or opt into this locale. Under the policy, language-specific behavior should either offer user choice or clearly justify the locale restriction.
The module docstring and run() docstring describe educational/tutorial content about building an AI agent, which implies explanatory or instructional behavior. In reality, the implementation imports a KnowledgeBase and persists supplied input and metadata via kb.store_concept(), which is a materially different operational intent.
The file’s user-facing title and runtime output are entirely in Chinese, and there is no indication that another language can be selected or that the locale restriction is intentional and documented. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
No suspicious patterns detected.