Threat reportSupply ChainTL-2026-6100
Sckit Supply Chain Worm Hits MemTensor npm & PyPI Packages (@memtensor/memos-cloud-openclaw-plugin, MemoryOS)
Malicious releases of the npm package @memtensor/memos-cloud-openclaw-plugin (0.1.21, 0.1.23, 0.1.25) and the PyPI package MemoryOS 2.0.34 bundle and launch a platform-specific Go native binary called 'sckit'. Static analysis shows credential-harvesting patterns and worm-like publishing/CI logic; exfiltration, credential reuse and reachability of the propagation code were not confirmed. First disclosed .
Key facts
| Identifiers | TL-2026-6100 |
|---|---|
| Also known as | sckit, Sckit supply chain worm |
| Severity | HIGH |
| First disclosed | |
| Affected products | MemTensor @memtensor/memos-cloud-openclaw-plugin (npm); MemTensor MemoryOS (PyPI) |
| Weaknesses (CWE) | CWE-506, CWE-829 |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1059 Command and Scripting Interpreter, T1071.001 Web Protocols, T1119 Automated Collection, T1195.002 Compromise Software Supply Chain, T1480 Execution Guardrails, T1528 Steal Application Access Token, T1552.001 Credentials In Files, T1583.001 Domains |
| Motivation | UNKNOWN |
| Target sectors | technology, software-development, artificial-intelligence |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 6 cited sources |
Detection coverage
As of 2026-11-14, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6100 across Splunk SPL, Microsoft KQL and Sigma, covering 28 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Sckit Implant Execution via Poisoned npm/PyPI Package (MemTensor OpenClaw / MemoryOS) — Exploitation
Detects the Go native 'sckit' implant being launched with the 'stage0 --config64' command line used by the launcher and the embedded GitHub Actions template, from a .sckit directory, or as a child of node/python (lib/sckit.js and memos/_stage0.py spawn it detached). Associated with malicious @memtensor/memos-cloud-openclaw-plugin 0.1.21/0.1.23/0.1.25 and MemoryOS 2.0.34 (TL-2026-6100). Behaviour-based and independent of hashes.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1195.002, T1059
- Data sources: sysmon, XmlWinEventLog:Microsoft-Windows-Sysmon/Operational, DeviceProcessEvents
- Severity: high
- Confidence: high
Splunk SPL
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h
| eval img=lower(Image), cmd=lower(CommandLine), parent=lower(ParentImage)
| where match(img, "[^a-z0-9_-]sckit([.]exe)?$") AND (match(cmd, "stage0|--config64") OR match(img, "[.]sckit[^a-z0-9_-]") OR match(parent, "[^a-z0-9_-](node|python[0-9.]*)([.]exe)?$"))
| stats count min(_time) as first_seen max(_time) as last_seen values(CommandLine) as command_lines values(ParentImage) as parents by host, User, Image
| convert ctime(first_seen) ctime(last_seen)
| table first_seen last_seen host User Image parents command_lines countMicrosoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("sckit", "sckit.exe")
| where ProcessCommandLine has_any ("stage0", "--config64")
or FolderPath contains ".sckit"
or InitiatingProcessFileName in~ ("node", "node.exe", "python", "python3", "python.exe", "pythonw.exe")
| project Timestamp, DeviceName, AccountName, FileName, FolderPath, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA256
| order by Timestamp descSigma
title: Sckit Implant Execution via Poisoned npm/PyPI Package
id: 3f6c1e52-8a41-4d7b-9c20-6e1d5b7a0f11
status: experimental
description: Detects execution of the Go implant sckit (stage0 --config64), from a .sckit folder or launched by node or python, as dropped by malicious MemTensor npm and PyPI packages (TL-2026-6100).
references:
- https://www.stepsecurity.io/blog/sckit-supply-chain-worm-hits-memtensor-npm-pypi-scopes
- https://github.com/MemTensor/MemOS-Cloud-OpenClaw-Plugin/issues/173
author: Threadlinqs Team
date: 2026-11-14
tags:
- attack.initial_access
- attack.t1195.002
- attack.execution
- attack.t1059
logsource:
category: process_creation
detection:
selection_img:
Image|endswith:
- '/sckit'
- '\sckit.exe'
selection_cli:
CommandLine|contains:
- 'stage0'
- '--config64'
selection_dir:
Image|contains:
- '/.sckit/'
- '\.sckit\'
selection_parent:
ParentImage|endswith:
- '/node'
- '\node.exe'
- '/python'
- '/python3'
- '\python.exe'
condition: selection_img and (selection_cli or selection_dir or selection_parent)
falsepositives:
- Unrelated internal tool also named sckit, verify path and signer
level: high
Known false positives:
- Unrelated internal tool or binary legitimately named sckit launched by node/python
- Security researchers detonating the sckit samples in a lab
Tuning notes: Sysmon for Linux and Windows both emit EventCode=1; change index/sourcetype if your Sysmon data lands elsewhere. Drop the parent-process clause if node/python launching a binary named sckit is common in your estate; allowlist signed internal tools by SHA256.
- Malicious MemTensor npm/PyPI Package Artifacts Written to Disk ([indicator], .sckit, [indicator]) — Exploitation · unlock with TL Creds
- Sckit PyPI CI Delivery Helper in GitHub Actions (twine-upload.sh / _pypi_bridge.sh) — Post-Exploitation · unlock with TL Creds
- Sckit Endpoint Connections to skyleen.fr Front Hosts and [indicator] — C2 · unlock with TL Creds
- Sckit Implant Binary Hash Match (npm and PyPI Payloads, All Platforms) — Exploitation · unlock with TL Creds
- Sckit Implant Spawning Publishing and Source-Control Tooling (Worm Propagation) — Post-Exploitation · unlock with TL Creds
- Sckit C2 HTTP Requests to skyleen.fr (/config, /status, /batch, initial-ci-v2) — C2 · unlock with TL Creds
- Sckit Runtime State Directory and CA Bundle Creation — Post-Exploitation · unlock with TL Creds
- Sckit C2 Front Host skyleen.fr and [indicator] Network Activity — C2 · unlock with TL Creds
Indicators of compromise
As of 2026-11-14, Threadlinqs Intelligence tracks 28 indicators of compromise for TL-2026-6100.
Sample indicators (3 of 28)
- IP address:
139.84.223[.]178 - Domain:
8a8acaf167b3[.]skyleen[.]fr - File hash:
381ac6dc1715d9298fe81b2a53a11f7b7d78e361ee3a6619ad54f8c4b062cc18
Defanged, TLP:CLEAR. Full set of 28 indicators: unlock with TL Creds.
Technical analysis
On 2026-09-23 (UTC) a series of npm versions of the OpenClaw AI-agent memory plugin @memtensor/memos-cloud-openclaw-plugin were published that differ from the clean 0.1.20 baseline (2026-08-03). Versions 0.1.21, 0.1.23 and 0.1.25 add lib/sckit.js and six platform-specific executables under .sckit/ (unpacked size grew from about 272 KB to about 43.6 MB); interleaved versions 0.1.22 and 0.1.24 restored clean contents in the examined artifacts. A GitHub issue (#173) reports that the malicious npm artifacts have no matching repository commits or tags, which points to a compromised publishing credential rather than a repository compromise. A PyPI release, MemoryOS 2.0.34 (import name memos), carries a similar payload.
The malicious npm versions have no install/preinstall/postinstall hook. Instead lib/sckit.js is called from the plugin's own logic at gateway startup and on every memory recall event. It starts the native binary as a detached child with ignored standard streams, an empty error handler, no deduplication or rate limiting, the full host environment, and (npm path) the user's prompt text in the SCKIT_EVENT_TEXT variable. A helper, collectStageZero(), maps NPM_TOKEN / NODE_AUTH_TOKEN into the child environment but is not called in the reproduced index.js. Version 0.1.25 adds lib/tls-trust.js and a bundled CA file (.sckit/ca-roots.pem) that sets SSL_CERT_FILE on Linux when no system CA bundle exists; it does not disable verification. In the PyPI package, memos/log.py triggers the payload via memos/_stage0.py after logging configuration succeeds, so a normal import of memos can reach it; the Python trigger passes no prompt text. memos/_pypi_bridge.sh only runs when invoked as /app/twine-upload.sh inside GitHub Actions with INPUT_PASSWORD set, then runs memos/_initial_ci_delivery.py, which verifies a signed index against an embedded Ed25519 key, downloads four SHA-256-checked assets, runs a pinned emitter and prints SCKIT_CI_RESULT_V2. Activation of this path and credential theft were not observed.
The decoded embedded configuration uses schema sckit.runtime.v1 with campaign profiles named cloud-openclaw-semi-nuclear (npm) and memos-semi-nuclear (PyPI), an inventory root of $HOME, state directories $HOME/.openclaw/.cache/runtime and $HOME/.memos/.cache/runtime, and three skyleen.fr front hosts per ecosystem using /config, /status and /batch paths. not_after values correspond to 2026-10-23 and are configured fields, not confirmed kill switches. Embedded regular expressions match AWS access key IDs, GitHub, GitLab, npm, PyPI and Hugging Face tokens, HashiCorp Vault, Slack, Stripe live and SendGrid keys, JWTs, and names associated with passwords, private keys, API keys, session cookies and connection strings. The Linux amd64 binary contains the module path supplychain.local/campaign/cmd/implant and function names such as recursivePublish, prepareRemoteNode, prepareRemotePython and prepareRemoteWorkflow, plus a GitHub Actions template running './%s/linux-amd64/sckit stage0 --config64 %q' on push. These strings suggest intended credential collection and spread across repositories and ecosystems but do not prove any workflow was installed or package published.
All findings are from static analysis; the binaries were not executed in the cited reports. No CVE, CVSS score or actor attribution is given in the sources. On 2026-10-30 the maintainers closed the GitHub issue, stating that 0.1.21, 0.1.23 and 0.1.25 were no longer in the registry and that latest was 0.2.0; token rotation and trusted-publishing status were not confirmed. Socket.dev lists the same three npm versions as containing malware. Severity HIGH is analyst judgment.
MITRE ATT&CK techniques by tactic:
Collection
T1005 Data from Local System; T1119 Automated Collection
Execution
T1059 Command and Scripting Interpreter
Command and Control
Initial Access
T1195.002 Compromise Software Supply Chain
Defense Evasion
Credential Access
T1528 Steal Application Access Token; T1552.001 Credentials In Files
Resource Development
Remediation
Patches
- npm: use a vetted version; 0.1.20 is the clean comparison baseline and the maintainers report latest is 0.2.0 (verify provenance)
- PyPI: remove or quarantine MemoryOS 2.0.34; no clean PyPI baseline was established in the source
Immediate actions
- Isolate hosts or CI runners that installed @memtensor/memos-cloud-openclaw-plugin 0.1.21, 0.1.23 or 0.1.25, or MemoryOS 2.0.34; stop the OpenClaw gateway, find detached 'sckit' child processes and preserve evidence
- Block skyleen.fr front hosts and 139.84.223.178 at DNS/proxy/egress and hunt logs for them
- Revoke and reissue credentials from a clean system, prioritizing npm/PyPI publishing tokens, GitHub/GitLab tokens, cloud keys, and secrets present in the process environment or home directory
- Review anything sensitive typed into the agent while an affected npm version was active (prompt text was passed in SCKIT_EVENT_TEXT)
Workarounds
- Disable the plugin, rebuild from trusted sources and refresh lockfiles and package caches
- If the PyPI publishing path may have run, review BASH_ENV, GITHUB_ENV changes and SCKIT_CI_RESULT_V2 output markers
Longer-term hardening
- Require 2FA and trusted publishing/provenance for npm and PyPI releases
- Enable package cooldown and compromised-update checks on dependency PRs
- Enforce egress allow-listing on CI runners (for example Harden-Runner allowed-endpoints)
- Audit downstream effects: package releases, workflow changes, repository changes and service access under reachable identities
Affected and fixed versions
- MemTensor — @memtensor/memos-cloud-openclaw-plugin (npm)
Vulnerable versions: 0.1.21; 0.1.23; 0.1.25
Fixed in: 0.1.20 (clean baseline); 0.2.0 (reported by maintainers as current latest) - MemTensor — MemoryOS (PyPI)
Vulnerable versions: 2.0.34
Timeline
- npm @memtensor/memos-cloud-openclaw-plugin 0.1.20 published; the last clean version and comparison baseline.
- GitHub issue #173 opened by a user reporting the malicious npm versions, and StepSecurity published its analysis covering the npm and PyPI (MemoryOS 2.0.34) payloads.
- Version 0.1.25 published at 04:36:58 UTC (0.1.24 at 04:33:30 was clean), re-adding the payload plus a TLS helper and CA bundle; latest pointed to 0.1.25 in StepSecurity's snapshot.
- Version 0.1.23 published at 03:49:20 UTC, re-introducing the payload about four minutes after 0.1.22.
- Version 0.1.22 published at 03:45:44 UTC with clean contents restored in the examined artifact.
- Version 0.1.21 published at 02:23:04 UTC adding locked-ioc-26 and six platform executables under .sckit/.
- Embedded not_after configuration values (2026-10-23 UTC) in both the npm and PyPI payloads; not confirmed to be kill switches.
- Maintainers closed issue #173, stating 0.1.21, 0.1.23 and 0.1.25 were absent from the registry and latest was 0.2.0; token rotation was not confirmed.
Sources cited
- Sckit Supply Chain Worm Hits MemTensor npm & PyPI Scopes (StepSecurity) stepsecurity.io · Research · 2026-09-23
- Socket.dev - @memtensor/memos-cloud-openclaw-plugin package page socket.dev · Research
- Socket.dev - memoryos PyPI package page socket.dev · Research
- StepSecurity Threat Center documentation docs.stepsecurity.io · Vendor report
- MemTensor incident report - GitHub issue #173 GitHub · Code repository · 2026-09-23
- StepSecurity Harden-Runner GitHub · Code repository
Further reading
Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.