registry / memgineering / 0.23.1
memgineering@0.23.1
One memory for the AI you connect. Recall, remember, and revise a brain your agents share — stored in your own folder.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has a real, lifecycle-reachable AI-agent configuration capability and its postinstall message pressures an agent to invoke it. The inspected source does not establish automatic config mutation, secret theft, remote payload execution, or a self-dependent lifecycle chain.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Global npm installation followed by an agent obeying the postinstall message and running memgineering setup.
Impact
An agent may be induced to open a browser and install guides or hooks into its host configuration without a direct user request.
Mechanism
Lifecycle-driven AI-agent setup and token-authenticated API requests.
AI rationale
The package has a real, lifecycle-reachable AI-agent configuration capability and its postinstall message pressures an agent to invoke it. The inspected source does not establish automatic config mutation, secret theft, remote payload execution, or a self-dependent lifecycle chain.
Evidence
package.jsonscripts/postinstall.mjsdist/index.js~/.claude/CLAUDE.md~/.claude/settings.json~/.codex/AGENTS.md~/.codex/hooks.json
Network endpoints2
api.memgineering.commemgineering.com
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- A postinstall hook runs on global installation.
- The hook directly instructs an AI agent to run setup immediately and open a browser.
- The setup command writes guides, skills, and hooks into detected Claude and Codex home directories.
- Runtime API requests can send a bearer token to the configured hosted endpoint.
Evidence against
- The postinstall script only prints guidance when npm reports a global install; it does not itself write agent files or make network requests.
- Setup has explicit dry-run and user-facing web options, and the shown lifecycle code says setup is not executed by postinstall.
- No self-dependency, obfuscated payload, shell execution, or secret harvesting was found in the inspected files.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
15function brandHome() {
L16: return process.env[BRAND.homeEnvVar] ?? join(homedir(), BRAND.homeDirName);
L17: }
...
L121: function isInteractive() {
L122: return Boolean(process.stdout.isTTY) && !jsonMode;
L123: }
L124: function printHuman(text) {
L125: if (!jsonMode) process.stdout.write(text + "\n");
L126: }
...
L137: for (let i = 0; i < input.length; i++) {
L138: const code = input.charCodeAt(i);
L139: if (code === 27 && input[i + 1] === "]" || code === 157) {
Critical
Credential Exfiltration
Findings
3 Critical3 High4 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
CriticalPrevious Version Dangerous Deltadist/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighCredential Redirect Persistencedist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Low
Affected versions and remediation
This report applies to memgineering@0.23.1.
See all versions of memgineering for other recorded verdicts.
- Review the evidence and your use of memgineering@0.23.1 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.