@netnodeag/kraftwerk@0.80.0
Open-source agentic workspace for teams — where people and AI agents get work done together: agents (Claude Code, Codex, Pi), skills, shared knowledge, repeatable workflows, and deterministic verification
AI Security Review
scanned 3d ago · by lpm-firewall-aiDaemon startup sends identifying user and machine details to the package's cloud service by default. The behavior is documented and can be disabled, but telemetry carrying a hostname and OS-derived user handle warrants a warning.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The daemon starts, including when launched as a configured login item.
Impact
The cloud service receives identifying details about the user and machine. The feature is documented and can be disabled with `kraftwerk cloud off`.
Mechanism
The daemon registers with the configured cloud endpoint and sends machine name, user handle, hostname, platform, and version; later heartbeats report workspace details.
AI rationale
Daemon startup sends identifying user and machine details to the package's cloud service by default. The behavior is documented and can be disabled, but telemetry carrying a hostname and OS-derived user handle warrants a warning.
Evidence
dist/cli/daemon.jsdist/server/cloud.jsdist/core/identity.jsdist/config.jsREADME.md~/.kraftwerk/identity.json~/.kraftwerk/relay.json~/.kraftwerk/cloud.json
Network endpoints1
srv.kraftwerk-cloud.netnode.cloud
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Starting the daemon automatically attempts to register the machine with the cloud and continues heartbeats.
- The registration includes the machine name, user handle, hostname, platform, and version; the default handle comes from the OS username.
- The default cloud endpoint is srv.kraftwerk-cloud.netnode.cloud, and the README says registration is on by default.
- The README documents the cloud registration and provides `kraftwerk cloud off` to disable it.
Evidence against
- The cloud registry is a described feature of the package, and registration is best-effort.
- The relay is separately controlled by relay settings; the reviewed daemon startup does not turn it on automatically.
- The manifest has no preinstall, install, or postinstall hook.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShellWebSocket
Source & flagged code
11 flaggeddist/remote.jsView file
1import { spawnSync } from "node:child_process";
L2: import { mkdir, stat } from "node:fs/promises";
High
dist/core/vibeables.jsView file
352cwd: r.dir,
L353: shell: true,
L354: detached: process.platform !== "win32",
High
bin/kraftwerk.jsView file
15if (existsSync(src) && process.env.KRAFTWERK_DIST !== "1") {
L16: const { register } = await import("tsx/esm/api");
L17: register();
Findings
2 Critical6 High5 Medium7 Low
CriticalTrojan Source Unicodeweb/dist/assets/editor-CE9TlKkJ.js
CriticalPrevious Version Dangerous Deltadist/cli/ui.js
HighChild Processdist/remote.js
HighShelldist/core/vibeables.js
HighSame File Env Network Executiondist/cli/daemon-control.js
HighCommand Output Exfiltrationdist/cli/daemon-control.js
HighRuntime Package Installdist/core/runner.js
HighSemantic Analysis Limiteddist/cli/daemon-control.js
MediumDynamic Requirebin/kraftwerk.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/cli/daemon-login.js
Affected versions and remediation
This report applies to @netnodeag/kraftwerk@0.80.0.
See all versions of @netnodeag/kraftwerk for other recorded verdicts.
- Review the evidence and your use of @netnodeag/kraftwerk@0.80.0 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.