@iamem/amem@0.4.4
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 default-on postinstall hook sends package and runtime metadata to the publisher’s domain. This is disclosed and does not include sensitive local data, but install-time telemetry is suspicious under the stated policy.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm postinstall during package installation, unless the opt-out, CI, or test condition applies.
Impact
The publisher can count installations and learn basic runtime/platform details; the reviewed payload does not expose credentials or local project data.
Mechanism
The hook POSTs package and runtime metadata to getamem.com/api/beacon/npm-install.
AI rationale
The default-on postinstall hook sends package and runtime metadata to the publisher’s domain. This is disclosed and does not include sensitive local data, but install-time telemetry is suspicious under the stated policy.
Evidence
package.jsonscripts/postinstall.jsdocs/npm-release.md
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs scripts/postinstall.js automatically as a postinstall hook.
- The hook sends the package name and version, Node version, platform, architecture, and timestamp to getamem.com.
- The package documents this as an anonymous install ping and provides an opt-out.
Evidence against
- The install beacon does not include credentials, hostnames, usernames, file contents, or local paths.
- The inspected CLI dispatches explicit commands; its backup scheduling and agent setup are user-invoked features.
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.4.4.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.4.4 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.