@melaya/runner@1.1.27
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no install lifecycle hook, but its runtime design combines server-directed local code execution with capture and reuse of third-party authenticated browser sessions. This is a concrete dangerous capability requiring a warning rather than a clean classification.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI with a runner token; subsequent server socket commands trigger pipelines and login flows.
Impact
A server controlling the runner connection can execute supplied pipeline code and receive or reuse authenticated third-party sessions.
Mechanism
Remote bundle execution and browser session capture.
AI rationale
The package has no install lifecycle hook, but its runtime design combines server-directed local code execution with capture and reuse of third-party authenticated browser sessions. This is a concrete dangerous capability requiring a warning rather than a clean classification.
Evidence
dist/sharedVendor.jsdist/connection.jsdist/lumaLogin.jsdist/lumaBrowserBridge.jsdist/linkedinLogin.js~/.melaya-runner/shared/~/.melaya-runner/shared-version.txt~/.melaya/luma/storage-state.jsonmain.py
Network endpoints3
wss://api.melaya.orgwww.linkedin.comluma.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- It downloads server-supplied bundle content with the runner token and writes it into a home-directory cache.
- It executes a Python pipeline after handling a server socket run command.
- It extracts LinkedIn and Luma authenticated session cookies and sends each login outcome over the socket.
- It persists the complete Luma browser storage state for later reuse.
- Its Luma bridge issues browser-context requests with included credentials, enabling use of the captured session.
Evidence against
- package.json has only a prepublish build hook, so installation does not automatically run the package.
- The observed login flows require an interactive browser sign-in and activation through a connected runner session.
- The package contains local model and browser-control functionality consistent with a remote pipeline runner, though the capability is high risk.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
8 flaggeddist/codeWorker.jsView file
51// model (--experimental-permission / --permission): fs read/write
L52: // limited to the scratch dir, child_process and worker_threads denied.
L53: //
High
Child Process
Package source references child process execution.
dist/codeWorker.jsView on unpkg · L51288// ulimit -t: hard CPU time in seconds.
L289: // We use /bin/sh -c "ulimit ...; exec sandbox-exec ..." so both limits
L290: // apply before the Node process starts. This is a soft-then-hard pair;
High
dist/browserProvisioner.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @melaya/runner@1.0.93
matchedIdentity = npm:QG1lbGF5YS9ydW5uZXI:1.0.93
similarity = 0.769
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical6 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/browserProvisioner.js
HighChild Processdist/codeWorker.js
HighShelldist/codeWorker.js
HighSandbox Evasion Gated Capabilitydist/browserProvisioner.js
HighCloud Metadata Accessdist/browserAuthz.js
HighRuntime Package Installdist/lumaLogin.js
HighSemantic Analysis Limiteddist/linkedinLogin.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdist/localRagIngest.py
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to @melaya/runner@1.1.27.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.27 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.