Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to support a real Zotero command-line workflow, but its install, update, and backup helpers include unsafe package-installation paths and weak handling of Zotero API-key backups.
Use the skill only if you are comfortable managing local Python tooling and Zotero API credentials. Prefer the pipx/PyPI install path, avoid curl | bash, git:// master installs, sudo pip, and --break-system-packages, and review any cron, PATH, alias, backup, or update script before running it. If you use backups, ensure the Zotero config and backup directory are readable only by your user account and revoke/regenerate the Zotero API key if it may have been exposed.
INSTALL.md:479Unverified Remote Installer Is Piped Directly into Bash
INSTALL.md:233Mutable Master Branch Is Installed over an Unauthenticated Git Transport
scripts/backup_restore.sh:52Zotero API-Key Backups Do Not Enforce Restrictive Permissions
scripts/update_check.sh:218Update Logic Uses an Inconsistent pip Executable and Reverses Installation Scope
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
otero-cli
zotcli configure
Follow the prompts to enter your Zotero userID and generate an API key.
For systems without PEP 668 restrictions or when using virtual environments.
Using user installation (recommended):
pip install --user zotero-cli
Ensure ~/.local/bin is in your PATH:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
Using virtual environment (best practice):
python3 -m venv ~/.venvs/zotero-cli
source ~/.venvs/zotero-cli/bin/activate
pip install zotero-cli
# To use zotero-cli later
source ~/.venvs/zotero-cli/bin/activate
zotcli configure
System-wide installation (not recommended on PEP 668 systems):
# This will fail on PEP 668-compliant systems
sudo pip install zotero-cli
# To force install (not recommended, potential for system conflicts)
sudo python3 -m pip install --break-system-packages zotero-
The instruction curl https://pyenv.run | bash fetches a remote script and immediately executes it in the shell without inspection or integrity verification. This creates a direct supply-chain and remote code execution risk if the remote content, transport, or DNS is compromised.
# Install pyenv
curl https://pyenv.run | bash
# Install Python 3.11
pyenv install 3.11
Piping curl output directly to bash combines network retrieval and execution in a single step, eliminating opportunities for inspection and making compromise of the upstream source immediately exploitable. In installation documentation this is especially dangerous because users often paste such one-liners verbatim.
# Install pyenv
curl https://pyenv.run | bash
# Install Python 3.11
pyenv install 3.11
This exact destructive target, rm -rf ~/.config/zotcli, is a true risky command because it forcefully removes user-specific application data. The context is legitimate uninstallation, but the lack of a strong warning keeps it security-relevant from a safe-docs perspective.
# Remove configuration directory
rm -rf ~/.config/zotcli
# Remove virtual environment (if used)
rm -rf ~/.venvs/zotero-cli
This exact destructive target, rm -rf ~/.config/zotcli, is a true risky command because it forcefully removes user-specific application data. The context is legitimate uninstallation, but the lack of a strong warning keeps it security-relevant from a safe-docs perspective.
# Remove configuration directory
rm -rf ~/.config/zotcli
# Remove virtual environment (if used)
rm -rf ~/.venvs/zotero-cli
This command force-deletes the application's virtual environment, which is destructive though not obviously malicious. Copy-paste execution errors around rm -rf make such documentation inherently risky without guardrails.
rm -rf ~/.config/zotcli
# Remove virtual environment (if used)
rm -rf ~/.venvs/zotero-cli
# Remove cloned repository (if installed from source)
rm -rf ~/zotero-cli
This command force-deletes the application's virtual environment, which is destructive though not obviously malicious. Copy-paste execution errors around rm -rf make such documentation inherently risky without guardrails.
rm -rf ~/.config/zotcli
# Remove virtual environment (if used)
rm -rf ~/.venvs/zotero-cli
# Remove cloned repository (if installed from source)
rm -rf ~/zotero-cli
This repository deletion command is potentially harmful because it can erase local work and any files placed in that directory. Its danger comes from forced recursive deletion rather than malicious intent.
rm -rf ~/.venvs/zotero-cli
rm -rf ~/zotero-cli
### Remove PATH Entries
This repository deletion command is potentially harmful because it can erase local work and any files placed in that directory. Its danger comes from forced recursive deletion rather than malicious intent.
rm -rf ~/.venvs/zotero-cli
rm -rf ~/zotero-cli
### Remove PATH Entries
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
# Debian/Ubuntu
sudo apt update && sudo apt install pipx -y
# Arch Linux
sudo pacman -S pipx
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
#### Option A: pipx (Recommended)
```bash
# Debian/Ubuntu
sudo apt update && sudo apt install pipx -y
# Arch Linux
sudo pacman -S pipx
The skill description frames the tool as a Zotero library interface, but the documented workflow also includes system package installation via apt and pip/pipx, remote version checks against PyPI/GitHub, and opening release pages. That broader behavior materially increases risk because it can lead to privileged system changes, network access, and software supply-chain exposure outside the expected Zotero task scope.
The skill description frames the tool as a Zotero library interface, but the documented workflow also includes system package installation via apt and pip/pipx, remote version checks against PyPI/GitHub, and opening release pages. That broader behavior materially increases risk because it can lead to privileged system changes, network access, and software supply-chain exposure outside the expected Zotero task scope.
The skill description frames the tool as a Zotero library interface, but the documented workflow also includes system package installation via apt and pip/pipx, remote version checks against PyPI/GitHub, and opening release pages. That broader behavior materially increases risk because it can lead to privileged system changes, network access, and software supply-chain exposure outside the expected Zotero task scope.
The skill description frames the tool as a Zotero library interface, but the documented workflow also includes system package installation via apt and pip/pipx, remote version checks against PyPI/GitHub, and opening release pages. That broader behavior materially increases risk because it can lead to privileged system changes, network access, and software supply-chain exposure outside the expected Zotero task scope.
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
h_process.sh'
alias zotsetup='~/zotero-cli/scripts/setup_and_check.sh'
alias zotbackup='~/zotero-cli/scripts/backup_restore.sh backup'
alias zotupdate='~/zotero-cli/scripts/update_check.sh update'
### 2. Make Scripts Executable
```bash
chmod +x *.sh *.py
For easier access, add scripts directory to PATH:
echo 'export PATH="$HOME/zotero-cli/scripts:$PATH"' >> ~/.bashrc
source ~/.bashrc
Then use without full path:
setup_and_check.sh
backup_restore.sh backup
Automate regular tasks:
# Weekly backup
0 9 * * 0 /path/to/backup_restore.sh backup
# Weekly update check
0 10 * * 0 /path/to/update_check.sh check
# Monthly cleanup
0 0 1 * * /path/to/backup_restore.sh clean
Create reusable template files:
# Create a template query file
cat > research_template.txt << 'EOF'
# Research queries template
#
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
..."
pipx install zotero-cli
;;
2)
echo ""
echo "Installing zotero-cli via pip --user..."
pip3 install --user zotero-cli
# Add to PATH if not already
if [[ ":$PATH:" != *":$HOME/.local/bin:"* ]]; then
echo ""
echo "Adding ~/.local/bin to PATH..."
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
export PATH="$HOME/.local/bin:$PATH"
fi
;;
3)
echo ""
echo "Manual installation instructions:"
echo ""
echo "1. Using pipx:"
echo " pipx install zotero-cli"
echo ""
echo "2. Using pip with user installation:"
echo " pip install --user zotero-cli"
echo ""
echo "3. Or, install from GitHub for latest version:"
echo " pip install git+git://github.com/jbaiter/
The chained command sudo apt update && sudo apt install pipx -y combines repository refresh and package installation in one privileged operation. This reduces user visibility and review points, so if the flow is triggered unexpectedly or modified later, it can enable rapid, opaque system changes under elevated privileges.
print_warning "pipx not found, installing..."
if check_command apt; then
sudo apt update && sudo apt install pipx -y
pipx ensurepath
export PATH="$HOME/.local/bin:$PATH"
else
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
chmod +x weekly_search.sh
crontab -e
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Create a simple research dashboard
cat > research_dashboard.sh << 'EOF'
#!/bin/bash
The natural-language instructions list English language as an inclusion criterion, which imposes a language restriction in the workflow. Under SQP-3, language or locale constraints should either be optional, user-selected, or clearly justified; this example presents the restriction as a default criterion without that context.
The guide suggests sudo pip install pipx as an option. Running pip with root privileges installs Python code from package indexes into privileged locations and is a well-known unsafe practice that can lead to system compromise if a package or dependency is malicious or tampered with.
Using pip (any system):
# Using system pip (if allowed)
sudo pip install pipx
# OR using user pip
pip install --user pipx
pipx ensurepath
The command sudo pip install zotero-cli instructs users to install the package and all dependencies with root privileges. This expands the blast radius of any malicious or compromised dependency and can overwrite system-managed Python files.
System-wide installation (not recommended on PEP 668 systems):
# This will fail on PEP 668-compliant systems
sudo pip install zotero-cli
# To force install (not recommended, potential for system conflicts)
sudo python3 -m pip install --break-system-packages zotero-cli
sudo python3 -m pip install --break-system-packages zotero-cli explicitly bypasses OS protections and performs a privileged install into system Python. This can destabilize the host and magnify the impact of a malicious dependency or typosquatted package.
sudo pip install zotero-cli
sudo python3 -m pip install --break-system-packages zotero-cli
**⚠️ Warning:** Using `--break-system-packages` is dangerous and can damage your system's Python installation. Use pipx or virtual environments instead.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
cd zotero-cli
#### Step 2: Create a Virtual Environment
```bash
python3 -m venv venv
No suspicious patterns detected.