registry / leviathan-of-hashem / 3.19.0
leviathan-of-hashem@3.19.0
Leviathan Shel HaShem — the 708-agent Kabbalistic swarm in your terminal. Self-contained binary, no Python/Node deps.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected source shows a package-aligned, user-invoked binary launcher with no install hooks, self-dependency chain, or concrete attack behavior. Unverified remote binaries limit assurance but do not establish maliciousness in this snapshot.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Invoking a declared CLI command loads the launcher; npm installation has no lifecycle trigger.
Impact
Execution of the downloaded CLI is expected functionality; the inspected source establishes no malicious effect. Remote binary contents remain unverified.
Mechanism
The launcher downloads and caches a platform executable, checks for updates, and runs it with caller arguments. This behavior matches the package's CLI structure.
AI rationale
The inspected source shows a package-aligned, user-invoked binary launcher with no install hooks, self-dependency chain, or concrete attack behavior. Unverified remote binaries limit assurance but do not establish maliciousness in this snapshot.
Evidence
.lvtn/binversion.txt
Network endpoints1
talon.leviathansi.xyz/releases/cli
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares CLI entrypoints without lifecycle hooks or runtime dependencies.
- All CLI wrappers load bin/run.js, which launches the binary with caller arguments and inherited environment.
- The launcher downloads a platform binary into its cache from a package-aligned release endpoint.
- Source inspection found no credential harvesting, exfiltration, broad project mutation, or agent configuration writes; the bundled older archive contains a similar launcher.
Evidence against
- Downloaded binaries are executed without integrity verification, and their contents are outside this static snapshot.
- CLI invocation can automatically update the cached binary or invoke pip as a fallback.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flagged · loading sourcebin/run.jsView file
11const path = require("path");
L12: const { spawn, execSync } = require("child_process");
L13:
High
124try {
L125: execSync(`powershell -Command "Unblock-File -Path '${BIN_PATH}'"`, { stdio: "ignore" });
L126: } catch (_) {}
High
7L8: const https = require("https");
L9: const http = require("http");
...
L11: const path = require("path");
L12: const { spawn, execSync } = require("child_process");
L13:
L14: const BASE = process.env.LVTN_BINARY_BASE || "https://talon.leviathansi.xyz/releases/cli";
L15: const CACHE_DIR = process.env.LVTN_CACHE_DIR ||
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/run.jsView on unpkg · L7Findings
5 High4 Medium5 Low
HighChild Processbin/run.js
HighShellbin/run.js
HighSame File Env Network Executionbin/run.js
HighSandbox Evasion Gated Capabilitybin/run.js
HighPrevious Version Dangerous Deltabin/run.js
MediumNetwork
MediumEnvironment Vars
MediumShips Compressed Blobleviathan-of-hashem-3.14.3.tgz
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNested Archive Needs Inspectionleviathan-of-hashem-3.14.3.tgz
LowNo License
Affected versions and remediation
This report applies to leviathan-of-hashem@3.19.0.
See all versions of leviathan-of-hashem for other recorded verdicts.
- Review the evidence and your use of leviathan-of-hashem@3.19.0 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.