@iamem/amem@0.1.3
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 malware chain or self-dependent lifecycle chain was found. Automatic outbound telemetry and explicit agent-control configuration are meaningful security-relevant behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm installation triggers telemetry; explicit init or backup schedule commands trigger configuration and persistence writes.
Impact
Installation metadata leaves the machine, and explicit commands can alter AI-agent settings or create user-level scheduled jobs.
Mechanism
Install-time telemetry plus user-invoked agent-hook and scheduler setup.
AI rationale
No concrete malware chain or self-dependent lifecycle chain was found. Automatic outbound telemetry and explicit agent-control configuration are meaningful security-relevant behavior.
Evidence
package.jsonscripts/postinstall.jsdist/cli.jsdist/install/claude.jsdist/backup-schedule.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- npm install automatically runs a postinstall script.
- The postinstall script sends package, Node, platform, architecture, and timestamp metadata to getamem.com.
- Explicit platform setup writes Claude Code hook commands into its settings file.
- Explicit backup scheduling creates and enables user-level scheduled tasks.
Evidence against
- The install beacon has a fixed host and sends only the constructed install-metadata object.
- Telemetry can be disabled with an environment variable and is skipped in CI and tests.
- Agent configuration writes are reached through explicit init or setup actions, not the install lifecycle.
- No self-dependency, payload download, secret harvesting, or remote code execution was found in the inspected paths.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
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 Deltadist/repo-identity.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.1.3.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.1.3 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.