@melaya/runner@1.1.28
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not an automatic install-time payload and includes some authorization checks, so the source does not establish malicious publication intent. Its server-delivered executable code and third-party session collection are nevertheless dangerous capabilities with material compromise impact.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the runner and connects it to a server that dispatches a pipeline or login request.
Impact
A compromised or malicious configured server could run code as the user and obtain reusable LinkedIn or Luma session credentials after the user signs in.
Mechanism
Server-supplied code execution and authenticated browser-session collection.
AI rationale
The package is not an automatic install-time payload and includes some authorization checks, so the source does not establish malicious publication intent. Its server-delivered executable code and third-party session collection are nevertheless dangerous capabilities with material compromise impact.
Evidence
dist/sharedVendor.jsdist/connection.jsdist/linkedinLogin.jsdist/lumaLogin.js~/.melaya-runner/shared/~/.melaya-runner/venv/~/.melaya/luma/storage-state.jsonmain.py
Network endpoints3
/api/v1/runner/shared-bundlewww.linkedin.comluma.com/signin
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The connected server can supply a Python bundle that the runner writes into its local cache.
- The runner then launches Python from that cache for server-dispatched pipeline runs.
- LinkedIn and Luma login flows extract session cookies and return them over the server socket.
- The package persists Luma browser storage state for later replay of authenticated actions.
Evidence against
- There are no npm install, preinstall, or postinstall hooks; the only lifecycle script is prepublishOnly.
- The remote bundle has a hash and HMAC verification step tied to the runner token.
- Browser authorization explicitly blocks metadata and private-network destinations.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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.692
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.28.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.28 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.