@cairnvibe/indexer@0.2.10
Cairn's analyzer and installer (the `cairn` CLI) — scans Next.js source or crawls any running app, and scaffolds the backend either way.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s setup wizard installs an automatic prebuild hook that reuses the configured LLM key on later builds, causing recurring external API calls and potential charges without a distinct opt-in. The provider choice and key prompt make the initial use expected, but do not establish consent to recurring paid calls on routine builds.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
After a user runs `cairn setup`, each later project build runs the inserted prebuild hook when the chosen provider key is configured.
Impact
Unexpected provider usage may incur charges and sends project source to the chosen provider during routine builds.
Mechanism
The hook invokes `cairn build`, which uses the configured Anthropic or Groq key to send scanned page source for manifest descriptions.
Attack narrative
Running `cairn setup` adds a prebuild hook that invokes the manifest build on future project builds. When the selected provider key is configured, that build sends page source to the provider and can incur API charges; setup offers no separate opt-in for those recurring calls.
AI rationale
The package’s setup wizard installs an automatic prebuild hook that reuses the configured LLM key on later builds, causing recurring external API calls and potential charges without a distinct opt-in. The provider choice and key prompt make the initial use expected, but do not establish consent to recurring paid calls on routine builds.
Evidence
dist/setup.jsdist/cli.jsdist/llm.jspackage.jsonui-manifest.json
Decision evidence
public snapshotAI called this Malicious at 84.0% confidence as Malware with low false-positive risk.
Evidence for block
- The CLI runs the setup wizard only when the user invokes `cairn setup`.
- Setup appends a `prebuild` script that runs `cairn build` on future project builds, without a separate opt-in for recurring provider calls.
- The wizard accepts an Anthropic or Groq key and uses it for manifest builds; the LLM client sends page source to the selected provider.
- The build writes the generated manifest to the project’s `ui-manifest.json`.
Evidence against
- The setup wizard asks the user to choose Anthropic, Groq, or skip, and prompts for a key.
- Manifest generation and provider calls are part of the package’s analyzer purpose.
- Setup’s usage text describes automatic manifest rebuilding on future builds.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/manifest.jsView file
4exports.parseApiCall = parseApiCall;
L5: const node_child_process_1 = require("node:child_process");
L6: function assembleManifest(rootDir, facts, l2, l3) {
High
dist/setup.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @cairnvibe/indexer@0.2.6
matchedIdentity = npm:QGNhaXJudmliZS9pbmRleGVy:0.2.6
similarity = 0.619
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/setup.jsView on unpkg170try {
L171: (0, node_child_process_1.execSync)(`npm install ${PACKAGES.join(" ")}`, { cwd: absDir, stdio: "pipe" });
L172: spinner.stop((0, ui_1.green)(`✓ installed ${PACKAGES.join(", ")}`));
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/setup.js
HighChild Processdist/manifest.js
HighRuntime Package Installdist/setup.js
HighAi Review Evidencedist/cli.js
HighAi Review Evidencedist/setup.js
HighAi Review Evidencedist/setup.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @cairnvibe/indexer@0.2.10.
See all versions of @cairnvibe/indexer for other recorded verdicts.
- Avoid installing @cairnvibe/indexer@0.2.10. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.