Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Loading npm security reports…

@zincapp/zn-vault-agent@1.23.0: Suspicious npm security report | LPM Firewall

Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Flagged as agent extension risk

Allowed by default with warning: install-time first-party agent extension setup was detected.

View on npm All versions Policy details

registry / @zincapp/zn-vault-agent / 1.23.0

@zincapp/zn-vault-agent@1.23.0

ZnVault Certificate Agent - Real-time certificate and secret distribution

AI Security Review

scanned 9h ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. No install-time behavior occurs. An explicit privileged setup creates a persistent service and root updater; a configured vault event can request package self-updates.

Static reason

No blocking static signals were detected.

Trigger

User runs `sudo zn-vault-agent setup`, then starts/configures the agent.

Impact

A configured vault or privileged local configuration can cause global package replacement; Payara mode substantially broadens the service account's sudo authority.

Mechanism

systemd persistence, vault-driven update trigger, and configured plugin loading

Rationale

The package is not concretely malicious, but it exposes dangerous privileged persistence and remote-triggered self-update capabilities. Flag as a warning for security review and deployment hardening.

Evidence

package.jsondist/commands/setup.jsdist/services/npm-auto-update.jsdist/lib/websocket.jsdeploy/scripts/zn-vault-agent-update.shdist/plugins/loader.js

Decision evidence

public snapshot

AI called this Suspicious at 87.0% confidence as Dangerous Capability with low false-positive risk.

© 2026 LPM Firewall

Product

Threat feed How it works Policy

LPM

LPM.dev Registry

Evidence for warning

dist/commands/setup.js creates root-owned systemd updater and sudoers rules.
Payara setup grants broad sudo commands including /usr/bin/env *, /usr/bin/bash *, kill, and pkill.
dist/services/npm-auto-update.js writes an update trigger that causes root npm global installation.
dist/lib/websocket.js accepts vault WebSocket update events even when periodic auto-update is off.

Evidence against

package.json has no preinstall, install, or postinstall hook.
Privileged setup is only reached through explicit root `setup` command and normally prompts.
The updater restricts target package, release channel, and semver in deploy/scripts/zn-vault-agent-update.sh.
Network target is user-configured vaultUrl; no hard-coded exfiltration endpoint found.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 84 file(s), 664 KB of source, external domains: 0.0.0.0, 127.0.0.1, github.com, vault.example.com

Source & flagged code

3 flagged · loading source

dist/plugins/loader.jsView file

183} L184: module = await import(resolvedPath); L185: }

Medium

Dynamic Require

Package source references dynamic require/import behavior.

dist/plugins/loader.jsView on unpkg · L183

dist/commands/setup.jsView file

34// non-default deployments; defaults match the standard host layout. L35: const PAYARA_USER = process.env.ZNVAULT_PAYARA_USER ?? 'payara'; L36: const PAYARA_HOME = process.env.ZNVAULT_PAYARA_HOME ?? '/opt/payara'; ... L51: const PAYARA_MEMORY_MAX = process.env.ZNVAULT_PAYARA_MEMORY_MAX ?? 'infinity'; L52: const __dirname = dirname(fileURLToPath(import.meta.url)); L53: /** ... L322: console.log(chalk.yellow(` - Remove configuration: ${CONFIG_DIR}/`)); L323: console.log(chalk.yellow(` - Remove data: ${DATA_DIR}/`)); L324: console.log(chalk.yellow(` - Remove logs: ${LOG_DIR}/`)); ... L427: Description=ZnVault Certificate Agent L428: Documentation=https://github.com/zincapp/zn-vault L429: After=network-online.target

Medium

Install Persistence

Source writes installer persistence such as shell profile or service configuration.

dist/commands/setup.jsView on unpkg · L34

deploy/scripts/zn-vault-agent-update.shView file

•path = deploy/scripts/zn-vault-agent-update.sh kind = build_helper sizeBytes = 1576 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

deploy/scripts/zn-vault-agent-update.shView on unpkg

Findings

6 Medium4 Low

MediumDynamic Requiredist/plugins/loader.js

MediumNetwork

MediumEnvironment Vars

MediumInstall Persistencedist/commands/setup.js

MediumShips Build Helperdeploy/scripts/zn-vault-agent-update.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

87%Warn

Verdict confidence

IntentDangerous Capability

TypeAgent extension lifecycle risk

False-positive riskLow

Review stagesource_first_review

Firewall policyWarn-only agent extension risk

Package metadata

npm

AuthorZincApp

Maintainerszincapp

Version1.23.0

PublishedJul 5, 2026

LicenseMIT

Dependencies11

Integrityverified

Package size320 KB

Files341

Keywordsznvaultcertificatesssltlsagent

LinksRepository Homepage Issues

Runtime surface

package.json

Entrypointsmain → dist/index.jstypes → ./dist/index.d.tsexports mapbin → zn-vault-agent

Runtimenode >=18

Artifact1.43 MB · 341 files1 signature(s) · provenance

Install lifecycleNo install hooks · other: build, build:bundle, dev, lint +8

Behavioral surface

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocketHighEntropyStringsUrlStringsManifest: clean

LPM CLI

Source & flagged code

3 flagged

dist/plugins/loader.jsView file

Lines 163-203javascript

163 }

164 /**

165 * Load a single plugin by config

166 */

167 async loadPlugin(config) {

168 const { package: packageName, path: localPath, config: pluginOptions } = config;

169 if (!packageName && !localPath) {

170 throw new Error('Plugin config must specify package or path');

171 }

172 const identifier = packageName ?? localPath ?? 'unknown';

173 log.debug({ package: packageName, path: localPath }, 'Loading plugin');

174 try {

175 let module;

176 if (localPath) {

177 // Resolve local path relative to config dir or as absolute

178 const resolvedPath = path.isAbsolute(localPath)

179 ? localPath

180 : path.resolve(process.cwd(), localPath);

181 if (!fs.existsSync(resolvedPath)) {

182 throw new Error(`Plugin file not found: ${resolvedPath}`);

183 }

184 module = await import(resolvedPath);

185 }

Medium

Dynamic Require

Package source references dynamic require/import behavior.

dist/plugins/loader.jsView on unpkg · L183

186 else if (packageName) {

187 // Import npm package from global node_modules

188 // Always use global npm to ensure consistent plugin versions across the system

189 const globalPackageDir = resolveGlobalPackageDir(packageName);

190 if (!fs.existsSync(globalPackageDir)) {

191 throw new Error(`Plugin package '${packageName}' not found in global npm. ` +

192 `Install it with: npm install -g ${packageName}`);

193 }

194 // ESM requires importing the actual entry point file, not just the directory

195 const entryPoint = resolvePackageEntryPoint(globalPackageDir);

196 log.debug({ packageName, globalPackageDir, entryPoint }, 'Loading plugin from global npm');

197 module = await import(entryPoint);

198 }

199 else {

200 throw new Error('Plugin config must specify package or path');

201 }

202 // Support both direct export and factory function

203 let plugin;

dist/commands/setup.jsView file

Lines 14-54javascript

14const LOG_DIR = '/var/log/zn-vault-agent';

15const CERT_DIR = '/etc/ssl/znvault';

16const SERVICE_FILE = `${SYSTEMD_DIR}/${SERVICE_NAME

deploy/scripts/zn-vault-agent-update.shView file

•path = deploy/scripts/zn-vault-agent-update.sh kind = build_helper sizeBytes = 1576 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

deploy/scripts/zn-vault-agent-update.shView on unpkg

}.service`

;

17const UPDATER_SERVICE_FILE = `${SYSTEMD_DIR}/${UPDATER_SERVICE_NAME}.service`;

18const SUDOERS_FILE = `/etc/sudoers.d/${SYSTEM_USER}`;

19const UPDATER_PATH_NAME = 'zn-vault-agent-updater';

20const UPDATER_PATH_FILE = `${SYSTEMD_DIR}/${UPDATER_PATH_NAME}.path`;

21const WRAPPER_INSTALL_DIR = '/usr/local/lib/zn-vault-agent';

22const WRAPPER_INSTALL_PATH = `${WRAPPER_INSTALL_DIR}/zn-vault-agent-update.sh`;

23const TRIGGER_FILE = `${DATA_DIR}/.update-trigger`;

24// Payara plugin integration. When this plugin is present, the agent must be able

25// to sudo (write setenv.conf, run asadmin as the payara user) — which the strict

26// base profile blocks (NoNewPrivileges + empty CapabilityBoundingSet). We detect

27// it and (a) emit the payara sudoers rules into the managed sudoers file, and

28// (b) drop in a unit override that re-grants the caps sudo needs. See

29// INC-2026-06-22 (setup clobbered the plugin's sudoers + strict profile broke

30// the plugin's startup sudo, taking Payara down).

31const PAYARA_PLUGIN_PACKAGE = '@zincapp/znvault-plugin-payara';

32const PAYARA_DROPIN_FILE = `${SYSTEMD_DIR}/${SERVICE_NAME}.service.d/20-payara-sudo.conf`;

33// The OS user Payara runs as, and its install root. Overridable via env for

34// non-default deployments; defaults match the standard host layout.

35const PAYARA_USER = process.env.ZNVAULT_PAYARA_USER ?? 'payara';

36const PAYARA_HOME = process.env.ZNVAULT_PAYARA_HOME ?? '/opt/payara';

37// Real install dir behind the /opt/payara symlink (→ /opt/payara7). systemd

38// ReadWritePaths usually resolves the symlink, but listing the real target too

39// is the robust choice across systemd versions. Overridable for non-default

40// layouts; '' (when PAYARA_HOME isn't symlinked) is filtered out.

41const PAYARA_HOME_REAL = process.env.ZNVAULT_PAYARA_HOME_REAL ?? '/opt/payara7';

42// Directory holding the deployed WAR (warPath). The deploy writes the WAR here,

43// so it must be writable under the agent's ProtectSystem=strict sandbox.

44const PAYARA_WAR_ROOT = process.env.ZNVAULT_PAYARA_WAR_ROOT ?? '/opt/zincapi';

45// Memory cap for the agent unit on Payara hosts. The agent SPAWNS the Payara JVM

46// (via `sudo -u payara ... start-domain`), so the JVM inherits the agent's

47// cgroup. The base unit caps it at 512M, which an 8GB-heap JVM cannot start

48// inside ("Failed to commit memory / Could not create the JVM", INC-2026-06-22).

49// On dedicated Payara hosts we lift the cap (default: infinity). Override with a

50// concrete value (e.g. '10G') via env if the host is shared.

51const PAYARA_MEMORY_MAX = process.env.ZNVAULT_PAYARA_MEMORY_MAX ?? 'infinity';

52const __dirname = dirname(fileURLToPath(import.meta.url));

53/**

Medium

Install Persistence

Source writes installer persistence such as shell profile or service configuration.

dist/commands/setup.jsView on unpkg · L34

54 * Detect whether the Payara plugin is installed for this agent. Checks the