registry / wimotek-chromium-sync / 1.0.8

wimotek-chromium-sync@1.0.8

Universal Chromium Session & Cookie Synchronizer with SSH Tunnel

AI Security Review

scanned 5d ago · by lpm-firewall-ai

The reviewed source shows no install-time behavior, import-time synchronization, or automatic collection sent to an unrelated host. Cookie and storage access occurs in the user-invoked synchronization flow and serves the package’s stated purpose.

Static reason

No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

Synchronization runs when the user invokes the CLI or calls the relevant API; importing the package alone does not start it.

Impact

Configured browser sessions may be read and copied to selected target nodes, as intended by the tool.

Mechanism

The tool connects to configured Chromium DevTools endpoints, optionally through SSH tunnels to configured hosts, and copies cookies and storage between configured browser contexts.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 90.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json declares no lifecycle scripts; its CLI points to bin/cli.js.
Importing chromium_sync exports the sync classes and merge helper without starting a sync.
The CLI defaults to a local node and runs synchronization only through its command flow.
SSH uses the host and credentials supplied in node configuration.
The tool reads browser cookies and storage, then applies them to configured target browser contexts as part of synchronization.

Evidence against

The intended functionality handles sensitive browser session data and can use SSH credentials, so its configured nodes and targets matter.
The npm manifest names a Python file as main, while the executable is a Node wrapper for the Python CLI.

Behavioral surface

Source

ChildProcess

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 342 B of source

Source & flagged code

10 flagged

chromium_sync/__init__.pyView file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

chromium_sync/__init__.pyView on unpkg

•path = chromium_sync/__init__.py kind = build_helper sizeBytes = 262 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

chromium_sync/__init__.pyView on unpkg

1""" wimotek-chromium-sync Package Universal Chromium Session & Cookie Synchronizer with SSH Tunnel and Cluster Support """ from .core import ChromiumSync, NodeConfig, merge_cookies __versio

Low

Ai Review Evidence

Importing chromium_sync exports the sync classes and merge helper without starting a sync.

chromium_sync/__init__.pyView on unpkg · L1

Findings

3 High1 Medium6 Low

HighSemantic Analysis Limitedchromium_sync/__init__.py

HighKnown Malware Source Similaritybin/cli.js

HighKnown Malware Source Fingerprint Signaturebin/cli.js

MediumShips Build Helperchromium_sync/__init__.py

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencechromium_sync/__init__.py

LowAi Review Evidencechromium_sync/cli.py

LowAi Review Evidencechromium_sync/core.py

Affected versions and remediation

This report applies to wimotek-chromium-sync@1.0.8.

See all versions of wimotek-chromium-sync for other recorded verdicts.

Review the evidence and your use of wimotek-chromium-sync@1.0.8 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: 2026-10-31 05:40:54.133Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.