@iamem/amem@0.6.0
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install hook sends bounded, disclosed telemetry to the package’s own website and provides an opt-out. Because the ping runs by default during installation, classify it as suspicious telemetry.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install or npx installation, unless AMEM_TELEMETRY_DISABLED is set or the environment is CI/test.
Impact
The publisher learns that the package was installed and the Node version, platform, and architecture; no credential or project data is sent in the inspected payload.
Mechanism
The postinstall hook sends a JSON npm_install event to the package publisher’s website.
AI rationale
The install hook sends bounded, disclosed telemetry to the package’s own website and provides an opt-out. Because the ping runs by default during installation, classify it as suspicious telemetry.
Evidence
package.jsonscripts/postinstall.jspackage.json (read)
Network endpoints1
getamem.com/api/beacon/npm-install
Decision evidence
public snapshotAI called this Suspicious at 98.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs scripts/postinstall.js as an npm postinstall hook.
- The hook sends an npm_install event containing package/version, Node version, platform, architecture, and timestamp.
- The event is POSTed to getamem.com at /api/beacon/npm-install.
- The README discloses the install ping and provides an opt-out; the hook skips only when opted out or in CI/test.
Evidence against
- The event contains package and runtime metadata, not credentials, project data, or file contents.
- The README identifies the ping as anonymous and documents AMEM_TELEMETRY_DISABLED=1.
- The backup persistence routine is reached through the explicit `amem backup schedule` command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
8 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
4 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Persistencedist/backup-schedule.js
HighSemantic Analysis Limiteddist/search.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/scan.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
Affected versions and remediation
This report applies to @iamem/amem@0.6.0.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.6.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.