owlmem@0.7.9
OwlMem command line: connect your AI apps to OwlMem in one command (npx -y owlmem install), an end-to-end encrypted vault for your AI agents, and a local MCP server.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and the reviewed network and shell behavior is tied to explicit OwlMem CLI or MCP operations. The scanner signals describe these package-aligned capabilities rather than a concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Network access and command execution occur when a user invokes CLI commands or MCP tools that need them.
Impact
No confirmed attack surface was established; the network and shell capabilities serve the requested vault operations.
Mechanism
The CLI sends the configured OwlMem token to its configured service base, defaults to https://owlmem.com, and retrieves vault items through its approval flow. Shell actions use caller-selected commands and secret references.
AI rationale
The manifest has no lifecycle hook, and the reviewed network and shell behavior is tied to explicit OwlMem CLI or MCP operations. The scanner signals describe these package-aligned capabilities rather than a concrete attack.
Evidence
package.jsonowlmem.mjs
Network endpoints1
owlmem.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines a CLI entrypoint and no install lifecycle hook.
- The CLI sends its configured OwlMem token to the OwlMem service base, which defaults to https://owlmem.com.
- The token comes from OWLMEM_TOKEN or the saved OwlMem configuration; requests use it for vault API calls.
- Vault reads decrypt returned ciphertext locally and use the approval flow for access.
- Shell execution is exposed through explicit run and vault_run actions with caller-selected commands and secret references.
Evidence against
- The package includes network access, saved-token use, and shell execution, but these support its documented vault CLI and MCP functions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedowlmem.mjsView file
41import { fileURLToPath } from "node:url";
L42: import { spawn, spawnSync } from "node:child_process";
L43:
High
436inputSchema: { type: "object", properties: {
L437: command: { type: "string", description: "Shell command to run (sh -c)" },
L438: env: { type: "object", description: 'Map of ENV_VAR to "item" or "item:field", e.g. {"DB_PASSWORD": "prod/db:password"}', additionalProperties: { type: "string" } },
High
41import { fileURLToPath } from "node:url";
L42: import { spawn, spawnSync } from "node:child_process";
L43:
L44: export const VERSION = "0.7.9";
L45: const BASE = (process.env.OWLMEM_URL || "https://owlmem.com").replace(/\/$/, "");
L46: const DIR = process.env.OWLMEM_HOME || join(process.env.XDG_CONFIG_HOME || join(homedir(), ".config"), "owlmem");
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
owlmem.mjsView on unpkg · L41Findings
7 High3 Medium3 Low
HighChild Processowlmem.mjs
HighShellowlmem.mjs
HighSame File Env Network Executionowlmem.mjs
HighCommand Output Exfiltrationowlmem.mjs
HighSandbox Evasion Gated Capabilityowlmem.mjs
HighTrigger Reachable Command Output Exfiltrationowlmem.mjs
HighSemantic Analysis Limitedowlmem.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to owlmem@0.7.9.
See all versions of owlmem for other recorded verdicts.
- Review the evidence and your use of owlmem@0.7.9 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.