Malicious code in @memtensor/memos-cloud-openclaw-plugin (npm)
Malicious versions of the npm package @memtensor/memos-cloud-openclaw-plugin published on September 23, 2026, contain a Go implant named sckit that runs automatically when the package loads. This implant collects various credential files from the user's home directory and exfiltrates them to attacker-controlled servers. It also has self-propagation capabilities to spread to other repositories and packages accessible with stolen credentials. The implant uses encrypted communication channels and deletes itself after execution. The affected versions are 0.1.21, 0.1.23, and 0.1.25.
AI Analysis
Technical Summary
On September 23, 2026, malicious versions 0.1.21, 0.1.23, and 0.1.25 of the npm package @memtensor/memos-cloud-openclaw-plugin were published containing a Go-compiled implant called sckit. This implant is bundled as a native binary for multiple OS/architecture targets and is automatically executed in the background upon package load. It collects credentials from files such as .npmrc, .pypirc, .git-credentials, SSH private keys, Vault tokens, and various token caches within the user's home directory. The implant exfiltrates stolen credentials to servers under skyleen.fr using an encrypted protocol involving CBOR, X25519 key exchange, and XChaCha20-Poly1305 encryption. It also includes functionality to copy itself into other repositories and packages accessible with the stolen credentials. The implant deletes its binary after execution to evade detection. The package's JavaScript source obfuscates the command and control server addresses and uses a configuration naming the campaign 'cloud-openclaw-semi-nuclear'. This is a credential theft and host compromise targeting users who install the package, not a typical plugin functionality.
Potential Impact
Any system that installs or runs the affected versions of @memtensor/memos-cloud-openclaw-plugin is fully compromised. The implant steals a wide range of credentials and tokens from the user's home directory, potentially exposing npm publishing tokens, SSH keys, Vault tokens, and other sensitive secrets. These credentials are sent to attacker-controlled servers, enabling further compromise and lateral movement. The implant can propagate itself to other repositories and packages accessible with stolen credentials, increasing the scope of compromise. Because the implant runs automatically on package load and deletes itself after execution, detection and remediation are challenging. The compromise affects the integrity and confidentiality of the affected systems and any credentials stored on them.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the affected package versions (0.1.21, 0.1.23, 0.1.25) is necessary. All credentials and secrets stored on the compromised system should be considered exposed and must be rotated immediately from a secure, uncompromised environment. Due to the implant's ability to propagate and persist, a full system compromise should be assumed, and affected systems should be thoroughly audited and potentially rebuilt. Monitoring for unusual network traffic to the specified skyleen.fr domains and related UUID paths may assist in detection. Users should avoid installing or using these malicious package versions.
Malicious code in @memtensor/memos-cloud-openclaw-plugin (npm)
Description
Malicious versions of the npm package @memtensor/memos-cloud-openclaw-plugin published on September 23, 2026, contain a Go implant named sckit that runs automatically when the package loads. This implant collects various credential files from the user's home directory and exfiltrates them to attacker-controlled servers. It also has self-propagation capabilities to spread to other repositories and packages accessible with stolen credentials. The implant uses encrypted communication channels and deletes itself after execution. The affected versions are 0.1.21, 0.1.23, and 0.1.25.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
On September 23, 2026, malicious versions 0.1.21, 0.1.23, and 0.1.25 of the npm package @memtensor/memos-cloud-openclaw-plugin were published containing a Go-compiled implant called sckit. This implant is bundled as a native binary for multiple OS/architecture targets and is automatically executed in the background upon package load. It collects credentials from files such as .npmrc, .pypirc, .git-credentials, SSH private keys, Vault tokens, and various token caches within the user's home directory. The implant exfiltrates stolen credentials to servers under skyleen.fr using an encrypted protocol involving CBOR, X25519 key exchange, and XChaCha20-Poly1305 encryption. It also includes functionality to copy itself into other repositories and packages accessible with the stolen credentials. The implant deletes its binary after execution to evade detection. The package's JavaScript source obfuscates the command and control server addresses and uses a configuration naming the campaign 'cloud-openclaw-semi-nuclear'. This is a credential theft and host compromise targeting users who install the package, not a typical plugin functionality.
Potential Impact
Any system that installs or runs the affected versions of @memtensor/memos-cloud-openclaw-plugin is fully compromised. The implant steals a wide range of credentials and tokens from the user's home directory, potentially exposing npm publishing tokens, SSH keys, Vault tokens, and other sensitive secrets. These credentials are sent to attacker-controlled servers, enabling further compromise and lateral movement. The implant can propagate itself to other repositories and packages accessible with stolen credentials, increasing the scope of compromise. Because the implant runs automatically on package load and deletes itself after execution, detection and remediation are challenging. The compromise affects the integrity and confidentiality of the affected systems and any credentials stored on them.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the affected package versions (0.1.21, 0.1.23, 0.1.25) is necessary. All credentials and secrets stored on the compromised system should be considered exposed and must be rotated immediately from a secure, uncompromised environment. Due to the implant's ability to propagate and persist, a full system compromise should be assumed, and affected systems should be thoroughly audited and potentially rebuilt. Monitoring for unusual network traffic to the specified skyleen.fr domains and related UUID paths may assist in detection. Users should avoid installing or using these malicious package versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-16476
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-mhjf-v53x-7p87"]
- Ecosystems
- ["npm"]
Threat ID: 6ab4be71f7a7c54106f0d461
Added to database: 09/24/2026, 06:08:49 UTC
Last enriched: 09/24/2026, 06:54:35 UTC
Last updated: 09/25/2026, 03:03:33 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.