@noctrodex/sast@1.0.0-rc13.3
NOCTRODEX(GHOSTMASTER) SAST thin client — browser login, auth and licence; fetches the verified host-side engine (Nuitka-obfuscated, self-contained runtime) and uses colibri as its only local AI backend. The engine runs on your own host and scans from you
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe normal launcher downloads or selects and executes an engine that the package explicitly describes as obfuscated with no readable source. Under the remote-code rule, executing concealed code is malicious even though the fetch is part of the advertised product purpose and uses an integrity check.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI normally, including its first launch; certificate trust is performed when the engine is resolved on Windows.
Impact
The opaque engine executes with the user's privileges, and on Windows its signer is added to trusted certificate stores. The package source does not establish what the engine does with those privileges.
Mechanism
The launcher fetches an engine archive from the vendor bucket, verifies its declared size and SHA-256, extracts it, then spawns the binary. The engine is explicitly documented as having no readable source. Windows setup adds its certificate to the current user's trusted stores.
Attack narrative
A normal CLI run resolves a separately hosted engine and starts it as a child process. The package says that engine is Nuitka-obfuscated and has no readable source, so its behavior cannot be established from the reviewable package. The launcher also adds the engine's shipped certificate to Windows trusted stores. The download's size and hash checks verify artifact integrity but do not make the concealed code reviewable.
AI rationale
The normal launcher downloads or selects and executes an engine that the package explicitly describes as obfuscated with no readable source. Under the remote-code rule, executing concealed code is malicious even though the fetch is part of the advertised product purpose and uses an integrity check.
Evidence
bin/noctrodex-sast.jslib/engine-fetch.jsREADME.md~/.local/share/noctrodex-sast/engine/~/.config/noctrodex-sast/engine-token%APPDATA%/noctrodex-sast/engine-token
Network endpoints3
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- Ordinary launcher invocation resolves an engine and starts it as a child process.
- The package documents that the engine has no readable source and is downloaded on first run.
- The launcher downloads and extracts a remote engine ZIP; the bucket path checks its SHA-256 before installation.
- On Windows, the launcher adds the shipped engine certificate to the current user's Root and TrustedPeople stores.
Evidence against
- There are no npm lifecycle scripts.
- The bucket download checks the engine ZIP's size and SHA-256.
- The engine download and execution are described as the package's intended operation.
- The engine token is attached only when the request URL shares the configured bucket's origin.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbin/noctrodex-sast.jsView file
15"use strict";
L16: const { spawn } = require("child_process");
L17: const { resolveEngine } = require("../lib/engine-fetch");
High
Child Process
Package source references child process execution.
bin/noctrodex-sast.jsView on unpkg · L15lib/engine-fetch.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @noctrodex/sast@1.0.0-rc13.2
matchedIdentity = npm:QG5vY3Ryb2RleC9zYXN0:1.0.0-rc13.2
similarity = 0.750
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
lib/engine-fetch.jsView on unpkg29const crypto = require("crypto");
L30: const { spawnSync } = require("child_process");
L31: const zip = require("./zip");
...
L33:
L34: const ENGINE_BASE_URL_DEFAULT = "https://noctrodex-engines.soumabha-majumdar.workers.dev/sast";
L35:
...
L38: function engineApi() {
L39: return (process.env.NOCTRODEX_ENGINE_API || process.env.NOCTRODEX_CORPUS_WORKER_URL ||
L40: "https://mcp.noctrodex-hq.com").replace(/\/$/, "");
Findings
1 Critical5 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltalib/engine-fetch.js
HighChild Processbin/noctrodex-sast.js
HighSame File Env Network Executionlib/engine-fetch.js
HighCommand Output Exfiltrationlib/colibri.js
HighSandbox Evasion Gated Capabilitylib/engine-fetch.js
HighTrigger Reachable Command Output Exfiltrationlib/colibri.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @noctrodex/sast@1.0.0-rc13.3.
See all versions of @noctrodex/sast for other recorded verdicts.
- Avoid installing @noctrodex/sast@1.0.0-rc13.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.