@hydranium/data-client-vscode
VS Code client primitives for the hydranium data-server protocol head; companion of @hydranium/data-server. The extension host relays the data-server's socket to a webview over a vscode-messenger hop, and the webview's data port reads it, so DataConnectio
This report shows the evidence for @hydranium/data-client-vscode@1.0.0-next.421. 1 of 68 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 8h ago · by lpm-firewall-aiThe inspected runtime behavior fits a VS Code data-client, but the manifest contains review-directed reassurance about lifecycle safety that appears intended to influence the verdict. I treated that reviewer manipulation as malicious intent.
Static reason
No blocking static signals were detected.
Trigger
Security review of package.json.
Impact
May bias a reviewer toward dismissing potential concerns without independently checking the source.
Mechanism
Manifest commentary makes strong reassuring claims about lifecycle behavior and publishing safety.
Attack narrative
The manifest includes unusually emphatic assurances that its prepack hook cannot affect installation and that publication is safe. This appears intended to steer review; the inspected runtime code otherwise implements the documented local socket and webview relay.
AI rationale
The inspected runtime behavior fits a VS Code data-client, but the manifest contains review-directed reassurance about lifecycle safety that appears intended to influence the verdict. I treated that reviewer manipulation as malicious intent.
Evidence
package.json
Decision evidence
public snapshotAI called this Malicious at 84.0% confidence as Malware with low false-positive risk.
Evidence for block
- The manifest contains unusually persuasive commentary asserting the prepack hook “cannot break the install” and describing the package as safe to publish, which appears aimed at steering security review.
Evidence against
- The declared scripts are build, cleanup, lint, tests, watch, and a prepack guard; no install lifecycle hook is declared.
- The inspected socket code connects to 127.0.0.1 by default, and the messenger code relays notifications between the extension host and its webview.
Behavioral surface
Source & flagged code
1 flaggedpackage.jsonView file
99"//prepack": "The publish guard, a `prepack` rather than a `prepare`: `prepack` runs only when a tarball is made (`npm pack`, `npm publish`) and never on install, so it cannot break the install it has no business touching. What it defends against: `files` lists `lib`, `lib` is gitignored, and a `files` entry matching nothing is skipped SILENTLY — so `npm publish` from an unbuilt tree emits a tarball of `src` and nothing else, with no error.",
High
Ai Review Evidence
The manifest contains unusually persuasive commentary asserting the prepack hook “cannot break the install” and describing the package as safe to publish, which appears aimed at steering security review.
package.jsonView on unpkg · L99Findings
1 High1 Low
HighAi Review Evidencepackage.json
LowScripts Present
Affected versions and remediation
This report applies to @hydranium/data-client-vscode@1.0.0-next.421.
The versions list below shows the verdict for each recorded version.
- Avoid installing @hydranium/data-client-vscode@1.0.0-next.421. 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.
Versions
68 known versions1.0.0-next.421latestshownMaliciousMalwareBlockPublishedNov 4, 2026, 11:48 AM1.0.0-next.420Clean—AllowPublishedNov 4, 2026, 11:34 AM1.0.0-next.419Unknown—AllowUnder ReviewNov 4, 2026, 11:15 AM1.0.0-next.412Clean—AllowPublishedNov 3, 2026, 4:35 PM1.0.0-next.411Unknown—AllowUnder ReviewNov 3, 2026, 3:01 PM1.0.0-next.406Unknown—AllowUnder ReviewNov 3, 2026, 10:07 AM1.0.0-next.405Clean—AllowPublishedNov 3, 2026, 9:46 AM1.0.0-next.401Unknown—AllowUnder ReviewNov 3, 2026, 12:31 AM1.0.0-next.400Unknown—AllowUnder ReviewNov 2, 2026, 11:46 PM1.0.0-next.396Unknown—AllowUnder ReviewNov 2, 2026, 4:05 PM1.0.0-next.392Clean—AllowPublishedNov 2, 2026, 9:52 AM1.0.0-next.391Clean—AllowPublishedNov 2, 2026, 2:05 AM1.0.0-next.387Unknown—AllowUnder ReviewNov 1, 2026, 11:47 PM1.0.0-next.386Unknown—AllowUnder ReviewNov 1, 2026, 11:29 PM1.0.0-next.384Unknown—AllowUnder ReviewNov 1, 2026, 10:27 PM1.0.0-next.382Clean—AllowPublishedNov 1, 2026, 7:42 PM1.0.0-next.381Clean—AllowPublishedOct 31, 2026, 12:01 PM1.0.0-next.380Unknown—AllowUnder ReviewOct 31, 2026, 11:44 AM1.0.0-next.379Clean—AllowPublishedOct 30, 2026, 4:04 PM1.0.0-next.378Clean—AllowPublishedOct 30, 2026, 3:47 PM1.0.0-next.376Unknown—AllowUnder ReviewOct 30, 2026, 1:08 PM1.0.0-next.375Unknown—AllowUnder ReviewOct 30, 2026, 11:41 AM1.0.0-next.373Clean—AllowPublishedOct 27, 2026, 9:53 PM1.0.0-next.372Clean—AllowPublishedOct 27, 2026, 8:32 PM1.0.0-next.371Unknown—AllowUnder ReviewOct 27, 2026, 7:30 PM1.0.0-next.370Clean—AllowPublishedOct 27, 2026, 3:02 PM1.0.0-next.369Unknown—AllowUnder ReviewOct 27, 2026, 2:46 PM1.0.0-next.367Clean—AllowPublishedOct 27, 2026, 12:12 PM1.0.0-next.366Unknown—AllowUnder ReviewOct 27, 2026, 11:35 AM1.0.0-next.365Clean—AllowPublishedOct 27, 2026, 11:22 AM1.0.0-next.364Clean—AllowPublishedOct 27, 2026, 9:45 AM1.0.0-next.363Clean—AllowPublishedOct 27, 2026, 1:23 AM1.0.0-next.362Unknown—AllowUnder ReviewOct 27, 2026, 1:00 AM1.0.0-next.361Unknown—AllowUnder ReviewOct 27, 2026, 12:32 AM1.0.0-next.360Clean—AllowPublishedOct 27, 2026, 12:12 AM1.0.0-next.359Unknown—AllowUnder ReviewOct 26, 2026, 11:56 PM1.0.0-next.358Unknown—AllowUnder ReviewOct 26, 2026, 11:41 PM1.0.0-next.357Clean—AllowPublishedOct 26, 2026, 11:24 PM1.0.0-next.356Clean—AllowPublishedOct 26, 2026, 4:57 PM1.0.0-next.354Unknown—AllowUnder ReviewOct 26, 2026, 4:39 PM1.0.0-next.353Unknown—AllowUnder ReviewOct 26, 2026, 4:16 PM1.0.0-next.351Clean—AllowPublishedOct 26, 2026, 2:28 PM1.0.0-next.350Clean—AllowPublishedOct 26, 2026, 2:10 PM1.0.0-next.348Clean—AllowPublishedOct 26, 2026, 1:27 PM1.0.0-next.344Unknown—AllowUnder ReviewOct 26, 2026, 11:04 AM1.0.0-next.341Unknown—AllowUnder ReviewOct 26, 2026, 10:35 AM1.0.0-next.340Clean—AllowPublishedOct 25, 2026, 7:25 PM1.0.0-next.339Unknown—AllowUnder ReviewOct 25, 2026, 7:07 PM1.0.0-next.338Clean—AllowPublishedOct 25, 2026, 6:15 PM1.0.0-next.335Clean—AllowPublishedOct 25, 2026, 5:30 PM1.0.0-next.334Clean—AllowPublishedOct 25, 2026, 4:40 PM1.0.0-next.333Clean—AllowPublishedOct 25, 2026, 4:13 PM1.0.0-next.332Unknown—AllowUnder ReviewOct 25, 2026, 4:00 PM1.0.0-next.331Unknown—AllowUnder ReviewOct 25, 2026, 3:50 PM1.0.0-next.330Unknown—AllowUnder ReviewOct 25, 2026, 3:35 PM1.0.0-next.328Unknown—AllowUnder ReviewOct 17, 2026, 12:19 PM1.0.0-next.327Unknown—AllowUnder ReviewOct 16, 2026, 6:19 PM1.0.0-next.326Unknown—AllowUnder ReviewOct 16, 2026, 4:27 PM1.0.0-next.325Unknown—AllowUnder ReviewOct 16, 2026, 1:06 PM1.0.0-next.324Unknown—AllowUnder ReviewOct 15, 2026, 10:18 PM1.0.0-next.323Unknown—AllowUnder ReviewOct 15, 2026, 8:44 PM1.0.0-next.322Unknown—AllowUnder ReviewOct 15, 2026, 6:23 PM1.0.0-next.321Unknown—AllowUnder ReviewOct 15, 2026, 3:11 PM1.0.0-next.320Unknown—AllowUnder ReviewOct 15, 2026, 2:41 PM1.0.0-next.319Unknown—AllowUnder ReviewOct 15, 2026, 11:24 AM1.0.0-next.318Unknown—AllowUnder ReviewOct 15, 2026, 10:40 AM1.0.0-next.317Unknown—AllowUnder ReviewOct 15, 2026, 1:07 AM1.0.0-next.315Unknown—AllowUnder ReviewOct 14, 2026, 11:30 PM