Run a FlareDeck agent on your own machine: it picks up cards assigned to it, works each one in a checkout of its own, and reports back on the card.
Blocked by LPM policy
Commands can access or alter anything available to the local user, and their output is sent to the FlareDeck service without per-command approval on this machine.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The changed dist/serve.js makes manager-supplied shell execution reachable in this version, and the command runs by default without local per-command approval. Because it enables arbitrary remote code execution as the user and returns output to FlareDeck, the package should be blocked despite the disclosed status message and opt-out switch.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The agent is serving and receives an `exec` event; the handler claims the request and runs it unless the user previously disabled remote commands locally.
Mechanism
The changed `dist/serve.js` wires `exec` events to `dist/remote-exec.js`, which runs the claimed command using `bash -lc` and posts stdout and stderr to the service.
Attack narrative
In 0.2.241, the changed `dist/serve.js` connects incoming FlareDeck `exec` events to a handler that claims the manager’s command, runs it through `bash -lc` as the local user, and sends its output back to FlareDeck. Remote commands are enabled by default and bypass the README-described command approval flow; only a separate local `remote off` action prevents execution.
382 { type: 'text', text: `This is the screen at ${viewport.width}×${viewport.height}. Judge only what is plain to see; never give a size in pixels.${takeStuckNote()}` },
// npx puts npm[redacted] in the environment, and the environment beats the config FILE
32// we just wrote — which is why `npm config set prefix` appeared to work and the install
⋯
58functionshellProfile() {
59const home = homedir();
60const shell = process.env['SHELL'] ?? '';
61const candidates = shell.includes('zsh')
62 ? ['.zshrc', '.zprofile', '.profile']
63 : ['.bashrc', '.bash_profile', '.profile'];
'never'
35});
⋯
44}
45/** `https://github.com/Owner/Repo(.git)` → `owner__repo`: the clone's folder name. */