init-simple-memorix
Audited by Socket on May 19, 2026
4 alerts found:
Anomalyx3MalwareThis is a configuration-only snippet that repeatedly triggers execution of an external command ('memorix.cmd hook') on multiple lifecycle events, including UserPromptSubmit. The snippet itself shows no explicit credential theft, network exfiltration, or obfuscation, but it creates a significant delegation sink whose real impact depends entirely on the unseen 'memorix.cmd hook' implementation and any context it can access during user-driven events. Review the referenced command/script for unintended data access, exfiltration, persistence, or other malicious behavior.
This configuration itself does not demonstrate explicit malware, but it enables broad, repeated execution of an external command (`memorix.cmd hook`) at key lifecycle stages, including after agent responses. The main supply-chain/security concern is the opaque behavior of `memorix.cmd` potentially recording or transmitting sensitive context. Review and verify the implementation, permissions, and data-handling/exfiltration behavior of `memorix.cmd` before trusting this hook configuration.
This fragment does not contain direct malicious logic, but it configures a host application to repeatedly execute an opaque external command (`memorix.cmd hook`) at several lifecycle events. The security posture therefore hinges on the provenance, integrity, and behavior of `memorix.cmd` and the hook execution mechanism; until those are reviewed, treat this as an elevated supply-chain risk (potential arbitrary code execution via hooks).
This fragment introduces high-risk, stealthy behavior by configuring lifecycle hooks that execute a Windows shell command (`cmd /c ...`) twice, while suppressing output (`show_output: false`). The actual impact depends entirely on what `memorix hook` resolves to and what it performs, but the capability and stealth characteristics are strong indicators that this package could perform harmful actions. Additional review should focus on the resolved `memorix` target (bundled vs PATH-based), the “hook” subcommand implementation, and any filesystem/network/credential access performed during these hook events.