@ngockhoale/ukit@3.4.50
Install/update an index-first AI workspace for Claude Code, OpenAI Codex and omp (Oh My Pi).
AI Security Review
scanned 18h ago · by lpm-firewall-aiInspected source confirms a runtime path that forwards existing Anthropic credentials to a package-selected default endpoint without recipient-specific consent. This concrete credential transfer supports blocking publication, even though it is not triggered by an npm lifecycle hook.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A runtime decision request runs through the configured shadow decision flow.
Impact
The endpoint receives a credential intended for the host’s Anthropic service without recipient-specific consent established in the inspected source.
Mechanism
The resolver falls back to an Anthropic key from the environment or Claude settings, then the client places it in an authentication header on a POST to the default decision endpoint.
Attack narrative
The shipped configuration enables shadow decision processing. When a runtime decision request uses that flow, UKit can reuse ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN from the host environment or Claude settings, attach it to an authenticated request, and send it to the default decision endpoint. The source provides endpoint and credential overrides, but does not establish recipient-specific consent for forwarding the existing Anthropic credential to that default host.
AI rationale
Inspected source confirms a runtime path that forwards existing Anthropic credentials to a package-selected default endpoint without recipient-specific consent. This concrete credential transfer supports blocking publication, even though it is not triggered by an npm lifecycle hook.
Evidence
template_project/ukit/storage/config.jsonsrc/core/gatewayProbe.jssrc/decision/client.jssrc/decision/shadow.js
Network endpoints1
openai.unicjsc.com
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The shipped runtime configuration sets decision processing to shadow stage.
- Without a lane-specific endpoint or key, the resolver selects the default decision host and can fall back to the host’s shared Anthropic credential.
- The fallback reads ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN from the environment or Claude settings.
- The client attaches the resolved key as an authentication header and sends a POST to the resolved endpoint.
- The shadow decision flow creates that client with the runtime environment and sends a decision batch.
Evidence against
- The credential transfer occurs in the runtime decision flow, rather than through an npm lifecycle hook. The source does not establish recipient-specific consent for sending the existing Anthropic credential to the default decision host.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemShell
HighEntropyStrings
Source & flagged code
11 flagged · loading sourcesrc/core/runtimeConfig.jsView file
9L10: const require = createRequire(import.meta.url);
L11: const { version: PACKAGE_VERSION } = require('../../package.json');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
src/core/runtimeConfig.jsView on unpkg · L9scripts/release/verify-release.mjsView file
•matchType = normalized_sha256
matchedPackage = @ngockhoale/ukit@3.4.54
matchedPath = scripts/release/verify-release.mjs
matchedIdentity = npm:QG5nb2NraG9hbGUvdWtpdA:3.4.54
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/release/verify-release.mjsView on unpkg1import { spawn } from 'node:child_process';
L2: import { readFileSync, writeFileSync, unlinkSync, existsSync } from 'node:fs';
...
L6:
L7: const rootDir = process.cwd();
L8: const npmCacheDir = path.join(os.tmpdir(), 'ukit-npm-cache');
...
L14: // UKIT_VERIFY_STEP_TIMEOUT_MS overrides the step budget for tests.
L15: const STEP_TIMEOUT_MS = Number(process.env.UKIT_VERIFY_STEP_TIMEOUT_MS) || 10 * 60 * 1000; // 10 min
L16: const REGISTRY_TIMEOUT_MS = Number(process.env.UKIT_VERIFY_REGISTRY_TIMEOUT_MS) || 60 * 1000; // 1 min
...
L18: // Opt-in post-publish registry-parity check (Release Policy invariant: npm and git always hold
L19: // the same latest version). Only meaningful AFTER `npm publish` — before publish the registry is
L20: // behind by definition — so it is gated behind --post-
Findings
8 High4 Medium5 Low
HighPayload In Excluded Dirtemplate_project/.claude/hooks/task-watchdog.sh
HighSemantic Analysis Limitedsrc/core/agentRuntime/artifacts.js
HighKnown Malware Source Similarityscripts/dev/capture-omp-stall.mjs
HighKnown Malware Source Similarityscripts/measure-decision-gateway.mjs
HighKnown Malware Source Similarityscripts/release/verify-release.mjs
HighKnown Malware Source Similaritysrc/core/agentRuntime/adapters.js
HighKnown Malware Source Similaritytemplate_project/.claude/ukit/runtime/handoff-intent.mjs
HighKnown Malware Source Similaritysrc/core/agentRuntime/supervisor.js
MediumDynamic Requiresrc/core/runtimeConfig.js
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to @ngockhoale/ukit@3.4.50.
See all versions of @ngockhoale/ukit for other recorded verdicts.
- Avoid installing @ngockhoale/ukit@3.4.50. 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.