Back to skill

Security audit

zhiliao

Security checks for vulnerabilities and agentic risk

Overview

The core news-tracking skill is understandable, but it ships with under-disclosed agent permissions and weak credential handling that users should review before installing.

Review or remove `.claude/settings.local.json` before installing, ignore and rotate any bundled API key, and configure your own `ZHILIAO_API_KEY`. Prefer an HTTPS base URL if the service supports it, restrict permissions on `~/.zhiliao/config.json`, and add cron jobs only deliberately because they will keep calling the API until removed.

Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Session Persistence

Medium
Category
Rogue Agent
Content
**方式二 — 配置文件(永久保存)**:

```bash
mkdir -p ~/.zhiliao
echo '{"apiKey":"your-api-key-here","baseUrl":"http://api-public.zhiliao.news"}' > ~/.zhiliao/config.json
```
Confidence
89% confidence
Finding
The skill instructs users to permanently store the API key in `~/.zhiliao/config.json` and uses an insecure `http://` base URL in that same configuration example. Persisting credentials on disk increases exposure to local compromise, and using plaintext HTTP could allow interception or modification of API traffic if the configured value is used.

Static analysis

No suspicious patterns detected.