registry / AI-agent control-surface risk / warden-ai

warden-ai

Verified context for AI coding agents. A local context layer that intelligently compresses, filters, indexes, and verifies AI coding-agent tool output. 32 MCP tools across 10 layers: code intelligence (tree-sitter, 30+ languages), context selection, tool

This report shows the evidence for warden-ai@0.7.1. 23 of 23 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 1mo ago · by lpm-firewall-ai

The package has a concrete automatic lifecycle chain that silently changes foreign AI-agent configuration and tool controls. This meets the install-control-surface blocking policy.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

npm postinstall

Impact

It can cause AI agents to invoke the package's server and redirect built-in tools in consumer projects.

Mechanism

The lifecycle hook runs init silently; init registers Warden, enables automatic approval, and installs agent hooks.

Policy narrative

On installation, postinstall silently runs the package CLI in the consumer directory. That CLI writes global agent configuration, grants Warden automatic tool approval, and installs project hooks that redirect agent tool calls. This is unconsented install-time mutation of broad AI-agent control surfaces.

AI rationale

The package has a concrete automatic lifecycle chain that silently changes foreign AI-agent configuration and tool controls. This meets the install-control-surface blocking policy.

Evidence

package.jsonbin/postinstall.cjsdist/cli.js.codex/config.toml.claude/settings.json.devin/hooks.v1.json

Decision evidence

public snapshot

AI identified this as a dangerous AI-agent capability at 99.0% confidence with low false-positive risk.

Evidence for policy risk

The manifest automatically runs a postinstall script.
The postinstall script silently invokes init in the consumer's current directory.
Init registers a server in global agent configurations and enables automatic tool approval.
Init writes PreToolUse hooks into consumer project agent settings.

Evidence against

No credential collection or outbound network send was identified in the inspected execution path.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsUrlStrings

Manifest

NoLicense

scanned 4 file(s), 1.04 MB of source, external domains: github.com, warden-io.vercel.app

Source & flagged code

10 flagged

package.jsonView file

Lines 54-94json

54 "benchmarks/HONEST-NUMBERS.md",

55 "README.md",

56 "LICENSE",

57 "TRADEMARK.md"

58 ],

59 "engines": {

60 "node": ">=22.5.0"

61 },

62 "scripts": {

63 "build": "tsup && tsc --emitDeclarationOnly --outDir dist",

64 "dev": "tsup --watch",

65 "typecheck": "tsc --noEmit",

66 "format": "prettier --write .",

67 "format:check": "prettier --check .",

68 "warden": "tsx src/cli/index.ts",

69 "serve": "tsx src/cli/index.ts serve",

70 "smoke": "tsx src/cli/index.ts status",

71 "test": "vitest run",

72 "test:watch": "vitest",

73 "prepublishOnly": "npm run build",

74 "postinstall": "node bin/postinstall.cjs"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L74

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L74

75 },

76 "dependencies": {

77 "@modelcontextprotocol/sdk": "1.29.0",

78 "@xenova/transformers": "2.17.2",

79 "chalk": "5.6.2",

80 "commander": "15.0.0",

81 "tree-sitter-wasms": "^0.1.13",

82 "web-tree-sitter": "^0.22.6",

83 "zod": "4.4.3"

84 },

85 "devDependencies": {

86 "@types/node": "26.1.1",

87 "prettier": "3.9.5",

88 "puppeteer": "^25.5.0",

89 "tsup": "8.5.1",

90 "tsx": "4.23.1",

91 "typescript": "7.0.2",

92 "vitest": "^4.1.10"

93 }

94}

bin/warden.jsView file

Lines 1-32javascript

1#!/usr/bin/env node

2// Warden CLI entrypoint. Delegates to the compiled CLI so the published

3// package works without tsx. In development, run via `npm run warden`.

4import { fileURLToPath } from "node:url";

5import { resolve, dirname } from "node:path";

6import { pathToFileURL } from "node:url"

dist/cli.jsView file

20Cross-file remote execution chain: dist/cli.js spawns dist/index.js; helper contains network access plus dynamic code execution. L20: import { fileURLToPath } from "url"; L21: var getFilename, getDirname, __dirname; L22: var init_esm_shims = __esm({ ... L612: init_guard(); L613: HEADER_RE = /^\s*(export\s+)?(async\s+)?(function|class|def|interface|type|enum|struct|impl|pub fn|fn|const|public|private|protected|static)\b.*$/; L614: IMPORT_RE = /^\s*(import\s+|from\s+\S+\s+import\s+|export\s+.*\s+from\s+|use\s+\S+::|#include\s+|require\s*\()/; ... L1949: function currentLevel() { L1950: const env = (process.env.WARDEN_DEBUG ?? "").toLowerCase(); L1951: if (env === "1" || env === "true" || env === "debug") return LEVELS.debug; ... L2040: try { L2041: parsed = JSON.parse(trimmed); L2042: } catc

High

Cross File Remote Execution Context

Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.

dist/cli.jsView on unpkg · L20

•matchType = normalized_sha256 matchedPackage = warden-ai@0.7.0 matchedPath = dist/cli.js matchedIdentity = npm:d2FyZGVuLWFp:0.7.0 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.

dist/cli.jsView on unpkg

bin/postinstall.cjsView file

•matchType = normalized_sha256 matchedPackage = warden-ai@0.7.0 matchedPath = bin/postinstall.cjs matchedIdentity = npm:d2FyZGVuLWFp:0.7.0 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.

bin/postinstall.cjsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = 1da75682d90f2f56 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = warden-ai@0.7.0 matchedPath = bin/postinstall.cjs matchedIdentity = npm:d2FyZGVuLWFp:0.7.0 similarity = 1.000 shingleOverlap = 3 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/postinstall.cjsView on unpkg

dist/index.jsView file

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

dist/index.jsView on unpkg

Source & flagged code

10 flagged · loading source

package.jsonView file

•scripts.postinstall = node bin/postinstall.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node bin/postinstall.cjs

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

bin/warden.jsView file

22// Compiled output not present — fall back to tsx for dev convenience. L23: const { spawn } = await import("node:child_process"); L24: const src = resolve(here, "..", "src", "cli", "index.ts");

High

Child Process

Package source references child process execution.

bin/warden.jsView on unpkg · L22

Findings

9 High5 Medium6 Low

HighInstall Time Lifecycle Scriptspackage.json

HighChild Processbin/warden.js

HighShell

HighCross File Remote Execution Contextdist/cli.js

HighKnown Malware Source Similaritybin/postinstall.cjs

HighKnown Malware Source Similaritydist/cli.js

HighKnown Malware Source Similaritydist/index.js

HighKnown Malware Source Similaritybin/warden.js

HighKnown Malware Source Fingerprint Signaturebin/postinstall.cjs

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumDynamic Requirebin/warden.js

MediumNetwork

MediumEnvironment Vars

Affected versions and remediation

This report applies to warden-ai@0.7.1.

The versions list below shows the verdict for each recorded version.

Avoid installing warden-ai@0.7.1. 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: 2026-09-20 05:38:22.273Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

23 known versions

0.7.1latestshownMaliciousSoft block: AI-agent control surfaceBlockPublishedAug 21, 2026, 11:53 AM 0.7.0MaliciousSoft block: AI-agent control surfaceBlockPublishedAug 20, 2026, 8:50 AM 0.6.1MaliciousSoft block: AI-agent control surfaceBlockPublishedAug 19, 2026, 4:10 PM 0.6.0MaliciousSoft block: AI-agent control surfaceBlockPublishedAug 19, 2026, 1:17 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other AI-agent control-surface risk packages

Runtime surface

Behavioral surface

Related packages

Other AI-agent control-surface risk packages

Source & flagged code