slaunt@0.1.24
⚠ Under reviewThis 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 readable source shows an explicit OAuth setup flow and no install-time hook, but enrollment passes a Slaunt access token to a native helper whose contents could not be inspected. That helper is central to credential handling and persistence, so the package needs manual review before its behavior can be determined.
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
A user runs `slaunt-hooks install` on a supported macOS system; setup then enrolls and registers the helper for background startup.
Impact
The helper's credential storage, network behavior, and background actions remain unverified, so the package's security behavior cannot be fully determined.
Mechanism
Setup sends the Slaunt access token and workspace identity to the helper over stdin. The shipped helper archive could not be inspected by the available offline analysis.
AI rationale
The readable source shows an explicit OAuth setup flow and no install-time hook, but enrollment passes a Slaunt access token to a native helper whose contents could not be inspected. That helper is central to credential handling and persistence, so the package needs manual review before its behavior can be determined.
Evidence
release/SlauntKillBar.zip.lpm-inspection-dWh8kc/0-0b30a1c91829.txtsrc/killbar-enrollment.jssrc/helper-release.js~/.claude.json~/.codex/config.toml~/.claude/settings.json~/.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 Manual Review at 87.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines only test scripts; it has no install lifecycle hook.
- The CLI reaches setup only when the user supplies the install command; help returns without starting setup.
- During that setup, the package passes a Slaunt access token and workspace identity to the native helper over stdin.
- The helper is shipped in a ZIP whose SHA-256 is checked, but the available offline analysis could not inspect the ZIP contents.
- The README describes the package as an OAuth handoff and guard for Codex and Claude Code.
Evidence against
- OAuth and setup requests use the package's stated Slaunt service, and setup requires an explicit sign-in flow.
- Launch agents and client configuration are installed by the explicit setup flow; no package lifecycle script does this automatically.
- The background updater asks for approval before applying an update.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
18 flaggedbin/slaunt-hooks.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = slaunt@0.1.23
matchedIdentity = npm:c2xhdW50:0.1.23
similarity = 0.957
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/slaunt-hooks.jsView on unpkg2'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
Findings
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.24.
See all versions of slaunt for other recorded verdicts.
- Review the evidence and your use of slaunt@0.1.24 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.