Skip to main content
Scans/npm/@memtensor/memos-local-openclaw-plugin

@memtensor/memos-local-openclaw-plugin

npm

Share

Summary

@memtensor/memos-local-openclaw-plugin v1.0.4 was classified as CRITICAL RISK with a risk score of 2397. Sigil detected 152 findings across 280 files, covering phases including provenance, install hooks, code patterns, obfuscation. Review the findings below before installing this package.

CRITICAL RISK(2397)

v1.0.4

22 March 2026, 16:32 UTC

by Sigil Bot

Risk Score

2397

Findings

152

Files Scanned

280

Provenance

Findings by Phase

Phase Ordering

Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.

install-makefile-curl

HIGH

Makefile/script pipes remote content to shell

package/README.md:99

```bash
curl -fsSL https://cdn.memtensor.com.cn/memos-local-openclaw/install.sh | bash
```
Why was this flagged?

A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.

install-npm-postinstall

CRITICAL

npm lifecycle script — runs automatically on install

package/openclaw.plugin.json:27

  "setup": {
    "postInstall": "node scripts/postinstall.cjs",
    "notes": [
Why was this flagged?

npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.

install-npm-postinstall

CRITICAL

npm lifecycle script — runs automatically on install

package/package.json:37

    "test:accuracy": "tsx scripts/run-accuracy-test.ts",
    "postinstall": "node scripts/postinstall.cjs",
    "prepublishOnly": "npm run build"
Why was this flagged?

npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.

install-pip-setup-exec

CRITICAL

setup.py executes code at install time

package/src/viewer/server.ts:216


  private get needsSetup(): boolean {
    return this.auth.passwordHash === null;
Why was this flagged?

This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.

Badge

Sigil scan badge for npm/@memtensor/memos-local-openclaw-plugin

Markdown

[![Sigil Scan](https://sigilsec.ai/badge/npm/@memtensor/memos-local-openclaw-plugin)](https://sigilsec.ai/scans/1273C69C-6479-40E7-AF0E-99DA82EBFAFA)

HTML

<a href="https://sigilsec.ai/scans/1273C69C-6479-40E7-AF0E-99DA82EBFAFA"><img src="https://sigilsec.ai/badge/npm/@memtensor/memos-local-openclaw-plugin" alt="Sigil Scan"></a>

Run This Scan Yourself

Scan your own packages

Run Sigil locally to audit any package before it touches your codebase.

curl -sSL https://sigilsec.ai/install.sh | sh
Read the docs →Free. Apache 2.0.

Early Access

Get cloud scanning, threat intel, and CI/CD integration.

Join 150+ developers on the waitlist.

Get threat intelligence and product updates

Security research, new threat signatures, and product updates. No spam.

Other npm scans

Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.

Scanned bySigil Bot