registry / @aspectlylabs/mikka / 0.0.344
@aspectlylabs/mikka@0.0.344
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged execution and network behavior supports running agents and relaying their model requests. The reviewed code showed no credential redirection to an unrelated fixed host or other concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the CLI or daemon and explicitly completes sign-in or starts an agent run.
Impact
No malicious impact was identified in the reviewed source.
Mechanism
Device authorization connects to the Mikka service; model API credentials are used by a local broker for provider requests.
AI rationale
The flagged execution and network behavior supports running agents and relaying their model requests. The reviewed code showed no credential redirection to an unrelated fixed host or other concrete attack behavior.
Network endpoints3
app.aspectlylabs.comapi.anthropic.comapi.openai.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest maps the mikka executable and library exports to package entry points.
- The CLI defaults to the Mikka service at https://app.aspectlylabs.com/mikka.
- Login uses a device authorization flow that displays a code for browser approval.
- The API-key broker defaults to the official Anthropic and OpenAI API endpoints.
- The broker validates HTTPS provider URLs and refuses redirected upstream requests.
- Sensitive credentials are filtered from the hosted child process environment.
Evidence against
- The daemon runs agent processes and makes network requests as part of its stated purpose.
- The daemon saves its device login credential locally.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
CopyleftLicense
Source & flagged code
6 flaggedgithub-credentials.mjsView file
7import { randomUUID } from 'node:crypto'
L8: import { spawn } from 'node:child_process'
L9: import { pathToFileURL } from 'node:url'
High
Child Process
Package source references child process execution.
github-credentials.mjsView on unpkg · L7mikka.jsView file
4601ai: "7.0.142",
L4602: execa: "10.1.1",
L4603: pino: "10.4.0",
High
6385assertSafeId("run id", runId);
L6386: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6387: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6396: }
L6397: async function pinnedGit(repoPath, worktree, env = process.env) {
L6398: const gitDir = await worktreeGitDir(repoPath, worktree);
L6399: const workTree = realpathSync4(worktree);
L6400: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6401: cwd: workTree,
Findings
5 High2 Medium5 Low
HighChild Processgithub-credentials.mjs
HighShellmikka.js
HighSame File Env Network Executionmikka.js
HighCredential Redirect Persistencemain.js
HighCommand Output Exfiltrationagents/native-container.mjs
MediumNetwork
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowCopyleft License
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @aspectlylabs/mikka@0.0.344.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.344 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.