📦
История аудитов
asoscan-setup - 1 аудит
Версия аудита 1 Последняя
15 нояб. 2026 г., 18:03
Most alerts reflect Markdown formatting, documented setup commands, or legitimate authentication to ASOScan; no evidence found of prompt injection or unauthorized exfiltration. Five findings identify plaintext credential persistence through shell configuration or persistent environment settings. Webhook verification guidance also omits a timestamp freshness check, leaving replay prevention unspecified.
1
Просканировано файлов
158
Проанализировано строк
10
Пункты проверки
0
Ложные срабатывания проигнорированы
Подтверждённые проблемы безопасности (1)
Средний
Webhook Verification Guidance Omits Replay Protection
The instruction to verify HMAC-SHA256 covers a timestamp and raw body but never requires timestamp freshness. A receiver following only this guidance could accept captured, validly signed events again.
The guidance specifies the signed timestamp but provides no expiry or replay check. This is incomplete receiver guidance, not evidence of an implemented vulnerable endpoint.
Пункты проверки возможностей (5)
Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.
Высокий
Hidden file in home directory
export ASOSCAN_API_KEY="asosk_live_..." # bash/zsh (add to ~/.zshrc to persist)
The comment recommends storing a live API key in a plaintext shell startup file. Backups, configuration sharing, or unintended readers could expose it.
Высокий
Generic API/secret keys
export ASOSCAN_API_KEY="asosk_live_..." # bash/zsh (add to ~/.zshrc to persist)
Although the example uses a placeholder, it tells users to persist their replacement key in shell configuration. This creates unnecessary plaintext credential storage.
Высокий
Generic API/secret keys
set -Ux ASOSCAN_API_KEY "asosk_live_..." # fish
Fish set -Ux persistently stores and exports the replacement API key. The example offers no warning about persistent plaintext storage or broader process exposure.
Высокий
Generic API/secret keys
setx ASOSCAN_API_KEY "asosk_live_..." # Windows PowerShell — open a new terminal after
Windows setx persists the replacement API key in user environment settings for future processes. This is unprotected credential persistence rather than session-only authentication.
Средний
Hidden file access
export ASOSCAN_API_KEY="asosk_live_..." # bash/zsh (add to ~/.zshrc to persist)
The suggested startup-file change persists a credential rather than an ordinary preference. No protected storage or file-permission guidance accompanies it.
Факторы риска
⚙️ Внешние команды (23)
SKILL.md:31 SKILL.md:33 SKILL.md:35 SKILL.md:46-53 SKILL.md:53-60 SKILL.md:60-62 SKILL.md:62-64 SKILL.md:64-65 SKILL.md:65-67 SKILL.md:67-68 SKILL.md:68-70 SKILL.md:70-71 SKILL.md:71-72 SKILL.md:72-74 SKILL.md:74-75 SKILL.md:75-76 SKILL.md:76-78 SKILL.md:78-80 SKILL.md:80-95 SKILL.md:95-109 SKILL.md:109 SKILL.md:68 SKILL.md:69
🌐 Доступ к сети (2)
📁 Доступ к файловой системе (2)
🔑 Переменные окружения (5)
Аудитор:: codex