slaunt@0.1.23
This package contains the client-side one-sign-in OAuth handoff for Codex and Claude Code. Each native client stores its own OAuth credentials; bootstrap credentials stay in CLI memory during setup. The Desktop vault is not used for the native OAuth hando
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged persistence, client configuration, OAuth, and updater code is reached through the CLI’s explicit setup flow and serves Slaunt’s stated integration purpose. The package has no lifecycle install hooks, and the inspected credential flow uses Slaunt’s configured issuer; no malicious behavior was established.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The user runs the CLI install command and selects Codex, Claude Code, or both; there are no npm lifecycle install scripts.
Impact
These actions modify selected client settings and install Slaunt background components as part of setup. No unrelated credential collection or attack behavior was identified.
Mechanism
The setup configures selected clients, performs Slaunt OAuth, enrolls its helper, installs related hooks and launch agents, and registers an updater that requests approval before applying releases.
AI rationale
The flagged persistence, client configuration, OAuth, and updater code is reached through the CLI’s explicit setup flow and serves Slaunt’s stated integration purpose. The package has no lifecycle install hooks, and the inspected credential flow uses Slaunt’s configured issuer; no malicious behavior was established.
Evidence
.claude.json.claude/settings.json.codex/config.toml.codex/hooks.json~/Library/LaunchAgents/ai.slaunt.killbar.cli.plist~/Library/LaunchAgents/ai.slaunt.claude-broker.plist~/Library/LaunchAgents/ai.slaunt.updater.plist
Network endpoints2
central-mcp-ccr-production.up.railway.appregistry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes an install command and has no npm lifecycle install scripts, so its setup flow does not run automatically during package installation.
- The CLI accepts an explicit install command and asks the user to select clients before setup proceeds.
- Setup sends OAuth credentials to the configured Slaunt issuer and installs Slaunt’s client configuration for the selected clients.
- The updater stages releases from the npm registry with scripts disabled and waits for approval before applying an update.
Evidence against
- Setup intentionally registers Slaunt helper and broker launch agents and installs hooks; these are product functions reached through the explicit setup flow.
- The source includes credential and network handling for Slaunt sign-in, but I found no evidence that credentials are sent to an unrelated host.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
18 flaggedbin/slaunt-hooks.jsView file
2'use strict';
L3: const {spawn}=require('node:child_process');
L4: const {ISSUER}=require('../src/setup-flow');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/slaunt-hooks.jsView on unpkg · L2src/desktop/broker-launch-agent.jsView file
3Trigger-reachable persistence chain: manifest.bin -> bin/slaunt-hooks.js -> src/install-flow.js -> src/desktop/broker-launch-agent.js
L3: const path=require('node:path');
L4: const net=require('node:net');
L5: const {execFile}=require('node:child_process');
L6: const {promisify}=require('node:util');
...
L9: const xml=s=>s.replace(/&/g,'&').replace(/</g,'<').replace(/>/g,'>').replace(/"/g,'"').replace(/'/g,''');
L10: function brokerPlist({node=process.execPath,script=path.join(__dirname,'broker-daemon.js')}={}){
L11: if(!path.isAbsolute(node)||!path.isAbsolute(script)||/[\x00-\x1f\x7f]/.test(node+script))throw new Error('broker-launch-invalid');
...
L15: try{const root=await fs.lstat(path.dirname(address)),socket=await fs.lstat(address);if(!root.isDirectory()||root.isSy
High
Trigger Reachable Persistence
A manifest entrypoint or package-local install chain reaches persistence behavior.
src/desktop/broker-launch-agent.jsFindings
13 High7 Medium6 Low
HighSandbox Evasion Gated Capabilitysrc/setup-flow.js
HighTrigger Reachable Persistencesrc/desktop/broker-launch-agent.js
HighShips High Entropy Blobrelease/SlauntKillBar.zip
HighKnown Malware Source Similaritysrc/updater.js
HighKnown Malware Source Similaritysrc/desktop/broker-launch-agent.js
HighKnown Malware Source Similaritysrc/killbar-enrollment.js
HighKnown Malware Source Similaritysrc/setup-flow.js
HighKnown Malware Source Similaritysrc/desktop/broker-keychain.js
HighKnown Malware Source Similaritysrc/hidden-oauth.js
HighKnown Malware Source Similaritysrc/native-config.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to slaunt@0.1.23.
See all versions of slaunt for other recorded verdicts.
- Review the evidence and your use of slaunt@0.1.23 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.