agent-bus@0.9.2
CAUTION· static onlyPublisher claims: "You have agents on Telegram, Discord, a coding assistant, and a research bot — but they can't talk to each other. Agent Bus fixes that. Drop a shared GitHub..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-20 and scored it 53/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Privileged sudo command; Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
"sudo |rm -rf|curl .* \| bash|wget .* \| sh"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."sudo |rm -rf|curl .* \| bash|wget .* \| sh"Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.chmod +x ~/agent-bus-repo/agent-bus.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.remote_sha = subprocess.check_output(['bash','-c','echo $REMOTE_SHA']).decode().strip() or 'unknown'Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…ebugging ### v0.7.0 (2026-03-30) - **`sync-acl` command**: Reads `shared/agents.json` and syncs all active pair partners into the local ACL whitelist (`allowReceiveFrom` + `allowSendTo`). Auto-invoked after `approve-pair` so new pairs can …Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."sudo |rm -rf|curl .* \| bash|wget .* \| sh"Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# memory-sync: display content and let the agent decide how to update MEMORY.mdFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.echo " Note: This is a memory-sync message. Review and decide whether to update your MEMORY.md."Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.chmod +x ~/agent-bus-repo/agent-bus.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x ~/agent-bus-repo/scripts/*.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
27 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim dr23334444: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.