@recallai/desktop-sdk@2.0.34
Recall Desktop SDK
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe install-time remote archive staging and later native execution are concrete supply-chain risk, but the inspected source does not show an attack or unrelated destination. Warn as a staged payload carrier.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation downloads and extracts an archive; calling SDK initialization later launches the native executable.
Impact
A compromised or unexpected archive could supply code that runs when the SDK is initialized; the inspected source does not establish that the archive is malicious.
Mechanism
setup.js fetches an archive from the Recall release bucket and extracts it into the package directory; index.js spawns the resulting platform executable.
AI rationale
The install-time remote archive staging and later native execution are concrete supply-chain risk, but the inspected source does not show an attack or unrelated destination. Warn as a staged payload carrier.
Evidence
setup.jsindex.js
Network endpoints1
recallai-desktop-sdk-releases.s3.us-east-1.amazonaws.com
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The install hook runs setup.js automatically.
- setup.js downloads platform archives from the Recall release bucket and extracts them into the package directory.
- index.js starts the extracted native executable when the SDK is initialized.
- The inspected source shows no credential forwarding or unrelated network destination.
Evidence against
- The download host is Recall-branded and the archive is selected using the package commit identifier.
- The native process starts through the SDK API, rather than during import.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 flaggedpackage.jsonView file
•scripts.install = node ./setup.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg15"install": "node ./setup.js",
"validate-types": "tsc --noEmit",
"build": "tsc -p tsconfig.bu
Medium
Suspicious Lifecycle Evidence
The install hook runs setup.js automatically.
package.jsonView on unpkg · L15index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @recallai/desktop-sdk@2.0.31
matchedIdentity = npm:QHJlY2FsbGFpL2Rlc2t0b3Atc2Rr:2.0.31
similarity = 0.500
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.
Findings
2 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltaindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidencesetup.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @recallai/desktop-sdk@2.0.34.
See all versions of @recallai/desktop-sdk for other recorded verdicts.
- Review the evidence and your use of @recallai/desktop-sdk@2.0.34 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.