@melaya/runner@1.1.34
Run Melaya AI pipelines locally with your own LM Studio or Ollama models
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not an install-hook malware chain, but it deliberately executes code supplied by a remote service and persists service-supplied modules. The capability is product-aligned yet creates unresolved high-impact risk if the service, account, or token is compromised.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs melaya-runner with a token and the connected server sends a pipeline run.
Impact
A compromised or malicious configured service can run arbitrary Python with the user's permissions and access the runner environment.
Mechanism
Remote Python payload download, cache write, and subprocess execution.
AI rationale
This is not an install-hook malware chain, but it deliberately executes code supplied by a remote service and persists service-supplied modules. The capability is product-aligned yet creates unresolved high-impact risk if the service, account, or token is compromised.
Evidence
dist/connection.jsdist/sharedVendor.jsdist/uvBootstrap.js~/.melaya-runner/shared/~/.melaya-runner/venv/tmpdir()/melaya-run-<runId>/main.py
Network endpoints2
api.melaya.orggithub.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- A connected server supplies Python source that is written locally and executed.
- The package fetches a mutable Python bundle from its service and stores its files in the user cache.
- Starting the CLI can automatically download and install an external uv executable.
Evidence against
- The manifest has no install-time lifecycle hook; prepublishOnly only builds before publishing.
- The behavior is consistent with a user-invoked remote pipeline runner, not a hidden install-time payload.
- Browser controls explicitly deny cloud-metadata and private-network destinations.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 flaggeddist/uvBootstrap.jsView file
20import { homedir, platform, arch } from "os";
L21: import { spawn, execSync } from "child_process";
L22: const CACHE_DIR = join(homedir(), ".melaya-runner");
High
Child Process
Package source references child process execution.
dist/uvBootstrap.jsView on unpkg · L20103if (asset.endsWith(".zip")) {
L104: // Windows only. PowerShell's Expand-Archive is always present and reliably
L105: // reads zips, unlike whatever `tar` happens to be on PATH.
High
dist/browserProvisioner.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @melaya/runner@1.0.93
matchedIdentity = npm:QG1lbGF5YS9ydW5uZXI:1.0.93
similarity = 0.538
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/uvBootstrap.js
HighShelldist/uvBootstrap.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.34.
See all versions of @melaya/runner for other recorded verdicts.
- Review the evidence and your use of @melaya/runner@1.1.34 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.