@lystech/core@3.0.129
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 1d ago · by lpm-firewall-aiInspected source confirms automatic creation of a consumer-project workflow and later repository metadata transmission to the package’s registry service. The behavior appears product-related and does not establish a concrete attack, so warn about the install-hook risk without blocking publication.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package in a project that lists it as a dependency, unless the setup skip conditions apply.
Impact
The consumer project gains an automatically created workflow and shares repository metadata with the registry service when that workflow runs.
Mechanism
The hook creates a workflow file that obtains repository identity and posts it to the package registry service on pushes or manual runs.
AI rationale
Inspected source confirms automatic creation of a consumer-project workflow and later repository metadata transmission to the package’s registry service. The behavior appears product-related and does not establish a concrete attack, so warn about the install-hook risk without blocking publication.
Evidence
package.jsonbin/postinstall.cjs.github/workflows/sync-package-registry.yml
Network endpoints1
lysbunback-usgg4.ondigitalocean.app
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The npm postinstall hook runs automatically and can write a workflow into a consuming project when that project lists this package as a dependency.
- The generated workflow sends the project owner, repository name, and repository ID to the package registry service on pushes or manual runs.
- The provider bundle also sends queued client events to its configured API base; the inspected code does not establish an unrelated recipient or credential theft.
Evidence against
- The workflow skips when SKIP_LYSTECH_SETUP is true, when the package is absent from the consumer’s dependency lists, or when the workflow file already exists.
- The registry workflow appears aligned with package update and registry setup; inspected source does not show destructive changes or arbitrary remote code execution.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
11 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/check-pwa.cjsView file
•matchType = normalized_sha256
matchedPackage = @lystech/core@3.0.126
matchedPath = bin/check-pwa.cjs
matchedIdentity = npm:QGx5c3RlY2gvY29yZQ:3.0.126
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/check-pwa.cjsView on unpkgFindings
3 Critical6 High5 Medium6 Low
CriticalCredential Exfiltrationdist/lystech-core-provider.umd.js
CriticalTrigger Reachable Dangerous Capabilitydist/lystech-core-provider.umd.js
CriticalPrevious Version Dangerous Deltadist/lystech-core-provider.umd.js
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Credential Exfiltrationdist/lystech-core-provider.umd.js
HighKnown Malware Source Similaritybin/attach.cjs
HighKnown Malware Source Similaritybin/check-pwa.cjs
HighKnown Malware Source Similaritybin/postinstall.cjs
HighKnown Malware Source Similaritybin/setup-registry.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
Medium
Affected versions and remediation
This report applies to @lystech/core@3.0.129.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.129 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.