registry / @botbuddy/cli / 1.63.16
@botbuddy/cli@1.63.16
⚠ Under reviewBotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source shows that the package ships native daemon binaries and can install them with elevated privileges. Their behavior could not be resolved through supported offline analysis, so a clean verdict is not justified and no attack is confirmed.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the daemon installation flow.
Impact
The binaries’ behavior and resulting effects cannot be determined from the available inspection.
Mechanism
The installer can place the platform binary in a root-owned location; available offline analysis could not inspect its executable behavior.
AI rationale
The source shows that the package ships native daemon binaries and can install them with elevated privileges. Their behavior could not be resolved through supported offline analysis, so a clean verdict is not justified and no attack is confirmed.
Evidence
.lpm-inspection-dCSYnJ/0-8516955d8e25.txt.lpm-inspection-dCSYnJ/1-a6d5ffb7686b.txtsrc/daemon/installer.mjsdaemon/bin/darwin-arm64/botbuddy-daemondaemon/bin/linux-x64/botbuddy-daemon
Decision evidence
public snapshotAI called this Manual Review at 98.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package includes daemon binaries in its published files.
- Offline analysis could not determine the behavior of either daemon binary.
- The installer can place a daemon binary in a root-owned location using sudo.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedsrc/update-check.mjsView file
15import { mkdir, readFile, writeFile } from "node:fs/promises";
L16: import { spawn, spawnSync } from "node:child_process";
L17: import { homedir } from "node:os";
High
Child Process
Package source references child process execution.
src/update-check.mjsView on unpkg · L15src/staging-pool/refresh-runtime.mjsView file
26const jobPath = join(app, "job.mjs");
L27: async function owned(path, directory = false, privateFile = false) {
L28: const info = await fs.lstat(path);
...
L42: const before = await configBytes();
L43: const installed = validateInstalledConfig(JSON.parse(before));
L44: const previous = installed.poolBinding;
...
L61: const rows = await fetchRegisteredPools({
L62: exec: (file, args, callOptions) => exec(process.execPath, [file, ...args], callOptions),
L63: botbuddyBin: cliEntry, env, tenant, poolId, preserveAgentContext: true, requireTenantMatch: true,
...
L125: await fs.rename(configTemp, configPath);
L126: return { ok: true, command: "refresh-runtime", tenant, poolId, runtimeVersion: metadata.version, runtimeSha256: contentDigest, personaAliases: Object.keys(next.personas), producer:
Medium
Install Persistence
Source writes installer persistence such as shell profile or service configuration.
Findings
5 High5 Medium3 Low
HighChild Processsrc/update-check.mjs
HighSame File Env Network Executionsrc/pw/daemon.mjs
HighTrigger Reachable Persistencesrc/staging-pool/cli.mjs
HighSemantic Analysis Limitedsrc/agent-credential-store.mjs#virtual:normalized:round1
HighPrevious Version Dangerous Deltasrc/stack.mjs
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencesrc/staging-pool/refresh-runtime.mjs
MediumShips Native Binarydaemon/bin/darwin-arm64/botbuddy-daemon
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @botbuddy/cli@1.63.16.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.16 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.