@iamem/amem@0.2.0
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete credential theft, remote payload execution, self-dependency chain, or destructive install behavior was found. The automatic telemetry beacon and explicit agent-control configuration are real capabilities that should not be treated as clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm installation triggers the beacon; amem init and backup schedule trigger configuration and persistence writes.
Impact
Installation metadata leaves the machine; later agent events or scheduled backups execute the package command locally.
Mechanism
Install-time telemetry plus user-invoked agent-hook and scheduler setup.
AI rationale
No concrete credential theft, remote payload execution, self-dependency chain, or destructive install behavior was found. The automatic telemetry beacon and explicit agent-control configuration are real capabilities that should not be treated as clean.
Evidence
package.jsonscripts/postinstall.jsdist/cli.jsdist/install/claude.jsdist/install/cursor.jsdist/backup-schedule.js~/.claude/settings.json~/.cursor/hooks.json~/.config/systemd/user/amem-backup.service~/.config/systemd/user/amem-backup.timer
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The npm postinstall hook automatically sends install metadata to getamem.com.
- The explicit amem init command writes Cursor and Claude hook configuration that runs amem on agent events.
- The explicit backup scheduling feature creates and enables per-user launch or timer persistence.
Evidence against
- The install beacon sends only package, runtime, platform, architecture, and timestamp fields; no credential or file collection was found.
- Agent configuration and backup scheduling are reached through explicit CLI or local UI actions, not the install hook.
- No self-dependency, downloaded payload execution, obfuscation, or destructive install-time behavior was found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node ./scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/app-shell.jsView file
28try {
L29: const require = createRequire(pkgJson);
L30: const bin = require("electron");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/app-shell.jsView on unpkg · L28Findings
3 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Persistencedist/backup-schedule.js
HighPrevious Version Dangerous Deltadesktop/main.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/app-shell.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/backup-schedule.js
MediumShips Build Helperscripts/mdm-offboard.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @iamem/amem@0.2.0.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.2.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.