registry / @viraatdas/rudder / 2.16.5
@viraatdas/rudder@2.16.5
A TUI for managing coding agents: run Claude Code, Codex and opencode side by side, each in its own isolated jj workspace.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found ordinary setup and user-invoked product behavior, with no concrete attack. The scanner's similarity and analysis-limit hints were not proof of malicious behavior.
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 package's postinstall hook runs during installation; cloud transfers and scheduled improvement require the corresponding user commands.
Impact
No unintended credential disclosure, broad agent configuration change, or other concrete attack was established.
Mechanism
The hook checks for jj and may invoke brew or cargo to install it. Cloud snapshots may stage local credentials for an authenticated Rudder cloud workflow.
AI rationale
Source inspection found ordinary setup and user-invoked product behavior, with no concrete attack. The scanner's similarity and analysis-limit hints were not proof of malicious behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- The manifest connects postinstall to its setup helper and lists only ws as a runtime dependency; the hook checks for jj and may install it using brew or cargo.
- The flagged Claude and Codex locations read local conversation or model data; the inspected excerpts show no transfer from those reads.
- Cloud code stages local credentials as part of snapshot creation and sends snapshots through an authenticated cloud workflow invoked by the cloud command.
- Scheduled improvement is installed through an explicit command; its default autonomy is propose, and collected task summaries are redacted and bounded.
- The board daemon binds to loopback, the version check queries the npm registry, and feedback submission requires user-provided text.
- Shared utility code places Rudder state in its user home or configured Rudder home. No concrete malicious behavior was identified in the inspected source.
Evidence against
- Cloud snapshots can include local credentials, but the inspected transfer belongs to the package's user-invoked cloud feature and uses its configured Rudder cloud service.
- Static similarity and parser-limit hints did not establish malicious behavior in the inspected source.
Source & flagged code
18 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/util.jsView file
•matchType = normalized_sha256
matchedPackage = @viraatdas/rudder@2.14.69
matchedPath = dist/util.js
matchedIdentity = npm:QHZpcmFhdGRhcy9ydWRkZXI:2.14.69
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/util.jsView on unpkgFindings
14 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighCredential Redirect Persistencedist/cloud.js
HighSandbox Evasion Gated Capabilityscripts/postinstall.mjs
HighTrigger Reachable Persistencedist/improve/schedule.js
HighSemantic Analysis Limiteddist/improve/collect.js
HighKnown Malware Source Similaritydist/util.js
HighKnown Malware Source Similaritydist/board/daemon.js
HighKnown Malware Source Similaritydist/handoff.js
HighKnown Malware Source Similaritydist/version-check.js
HighKnown Malware Source Similaritydist/feedback.js
HighKnown Malware Source Similaritydist/improve/state.js
Affected versions and remediation
This report applies to @viraatdas/rudder@2.16.5.
See all versions of @viraatdas/rudder for other recorded verdicts.
- Review the evidence and your use of @viraatdas/rudder@2.16.5 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.