tdem-electron-sdk@0.4.3
tdem sdk for electron applications
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source supports a telemetry SDK with explicit runtime activation rather than an install-time malware chain. Its preload mutation and configurable HTTP/body collection are broad enough to warrant a warning while no concrete malicious payload or account hijack was verified.
Decision evidence
public snapshot- Runtime initialization can add the package preload to an Electron session's existing preload list.
- The renderer HTTP monitor can collect configured request headers, response headers, and request or response bodies for telemetry.
- Optional nodeInjection enables a child-process injection integration.
- package.json has no npm install lifecycle hook; its only lifecycle script is prepublishOnly.
- The main initializer requires a non-empty project ID and an explicit HTTP(S) collector URL.
- No source evidence showed credential theft, account-setting changes, remote code loading, or automatic execution on install.
Source & flagged code
7 flaggedPackage source references child process execution.
scripts/assert-node-sdk-published.jsView on unpkg · L5Package source references dynamic require/import behavior.
scripts/assert-node-sdk-published.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to tdem-electron-sdk@0.4.3.
See all versions of tdem-electron-sdk for other recorded verdicts.
- Review the evidence and your use of tdem-electron-sdk@0.4.3 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.