@lystech/core@3.0.124
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic postinstall creates a persistent consumer CI workflow and enables later repository metadata transfer. This supports a warning for install-time mutation, but the inspected source does not establish a block-eligible attack.
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
The package's postinstall runs in a consumer project that declares @lystech/core and lacks the target workflow file.
Impact
This creates an unrequested persistent CI workflow and shares repository identification data with the package registry.
Mechanism
The script writes .github/workflows/sync-package-registry.yml; on later pushes or manual workflow dispatch, that workflow sends repository metadata to the registry endpoint.
AI rationale
The automatic postinstall creates a persistent consumer CI workflow and enables later repository metadata transfer. This supports a warning for install-time mutation, but the inspected source does not establish a block-eligible attack.
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 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs bin/postinstall.cjs automatically after installation.
- The postinstall skips when the consumer project itself is @lystech/core, but otherwise can create a GitHub Actions workflow in the consumer project.
- That workflow contacts the package registry endpoint to register or remove the consumer repository.
Evidence against
- The workflow is created only when the consumer project includes @lystech/core and the workflow file is absent.
- The source does not show credential collection or a write to an AI-agent control surface.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
10 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 = previous_version_dangerous_delta
matchedPackage = @lystech/core@3.0.114
matchedIdentity = npm:QGx5c3RlY2gvY29yZQ:3.0.114
similarity = 0.571
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/check-pwa.cjsFindings
3 Critical5 High5 Medium6 Low
CriticalCredential Exfiltrationdist/lystech-core-provider.umd.js
CriticalTrigger Reachable Dangerous Capabilitydist/lystech-core-provider.umd.js
CriticalPrevious Version Dangerous Deltabin/check-pwa.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Credential Exfiltrationdist/lystech-core-provider.umd.js
HighKnown Malware Source Similaritybin/attach.cjs
HighKnown Malware Source Similaritybin/postinstall.cjs
HighKnown Malware Source Similaritybin/setup-registry.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/check-pwa.cjs
MediumNetwork
Affected versions and remediation
This report applies to @lystech/core@3.0.124.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.124 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.