What happened to the MemTensor packages?
In its analysis, StepSecurity says three releases of MemTensor's OpenClaw memory plugin on npm and one MemoryOS release on PyPI were published on September 23, 2026 with a launcher for a cross-platform binary called sckit. The npm launcher has no install hook: it runs from the plugin's gateway startup and memory-recall code, which gets around --ignore-scripts. The PyPI launcher fires from memos/log.py logging setup.
StepSecurity says the binary's strings match cloud, source-control, registry and AI-service credential patterns, and that the npm recall path passes user prompts to it. Strings also suggest a propagation capability, but StepSecurity confirms neither exfiltration nor propagation. It notes no PyPI release is a known-clean baseline yet.
Which MemTensor versions are affected?
- npm
@memtensor/memos-cloud-openclaw-plugin0.1.21, 0.1.23 and 0.1.25. 0.1.22 and 0.1.24 are clean, and 0.1.20 is the baseline. - PyPI
MemoryOS2.0.34 (import namememos). - Agents and gateways that loaded the plugin, including prompts entered while it was active.
How to check if you're affected
- Search repositories, lockfiles and developer machines for the affected versions.
- Look for
.sckitexecutables launched by the gateway or by Python logging, and the command patternsckit stage0 --config64. - Check DNS and proxy logs for subdomains of
skyleen.fr, and look forlib/sckit.js,lib/tls-trust.jsandmemos/_pypi_bridge.sh.
What to do now
- Isolate affected hosts, stop the gateway and kill detached sckit processes after preserving evidence.
- Disable the plugin, return npm to 0.1.20 and quarantine MemoryOS 2.0.34.
- From a clean system, revoke publishing tokens first, then source-control and cloud credentials.
- Review prompts entered into the agent while the npm plugin was active, and audit downstream releases and workflow changes.
Why --ignore-scripts wasn't enough
Disabling install scripts is a common supply chain control, and sckit sidestepped it by running from normal application code paths instead of an install hook. Once a package is imported or a plugin starts, its code runs with the app's permissions. That's why version pinning, review of new releases and a short cooldown before adopting fresh versions matter as much as install-time controls.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify finds every repository and container image that pulls an affected package version and runs the upgrade as one campaign, scoped by CVE, package, repo or team, with owners, Slack escalation and SLA tracking. Your developers approve every merge.
Nullify can't tell you whether the payload ran on a given machine or runner. Use the checks above for that, then fix the dependency everywhere it appears.
Frequently Asked Questions
Which MemTensor packages were compromised?
npm @memtensor/memos-cloud-openclaw-plugin 0.1.21, 0.1.23 and 0.1.25, and PyPI MemoryOS 2.0.34, all published September 23, 2026. Use npm 0.1.20 as the baseline; StepSecurity says no PyPI release is a known-clean baseline yet.
Does --ignore-scripts protect against sckit?
No. The npm launcher runs from the plugin's gateway startup and memory-recall code, not an install hook, and the PyPI launcher runs during logging setup. Disabling install scripts doesn't stop either path.
What does sckit steal?
StepSecurity says its strings match cloud, source-control, registry and AI-service credential patterns, and the npm path passes user prompts to it. It hasn't confirmed exfiltration or propagation, so treat affected hosts as compromised and rotate credentials.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.