One campaign across two registries
Socket reports malicious npm releases of @memtensor/memos-cloud-openclaw-plugin at 0.1.21, 0.1.23 and 0.1.25, plus MemoryOS 2.0.34 on PyPI. The package names serve different integration paths, but the research describes a shared credential-collection payload. An inventory limited to one language ecosystem can therefore miss related exposure.
The version list comes from Socket’s analysis at publication time. Registry availability and any subsequent clean release can change; operators should use current upstream and registry records for replacement decisions. A package name in a dependency file alone does not prove a malicious version was installed or executed.
What execution can reach
The report describes a bundled Go binary named sckit for major desktop and server platforms. In the npm plugin, the binary starts with the OpenClaw gateway and during memory recall. In the Python package, it starts when the memos module is imported. Those trigger points matter when deciding which hosts and logs to examine.
Socket’s static analysis indicates the binary searches for npm, PyPI, GitHub, GitLab, AWS, Vault and SSH secrets. The report supports a credential-theft capability. It does not establish that every installation had those secrets, or that every attempted exfiltration succeeded.
Investigate before replacing
Correlate exact installed versions with execution history, process context and available credentials. Preserve artifacts and network evidence where feasible, then remove affected installations and rotate at-risk credentials from a clean host. Review publishing tokens as well as application secrets because both package ecosystems appear in the reported target set.
Use the linked original analysis for indicators and current maintainer notices for package status. Do not substitute a guessed safe version for a verified registry or maintainer update.
Evidence and review
Incident date: Unknown. Evidence checked .
Merged by pankajmouriya · Editorial merge