@lystech/core@3.0.140
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 4h ago · by lpm-firewall-aiSource confirms an automatic install hook that writes a repository workflow and a later registry interaction. This is a real install-time capability with an opt-out, but the inspected source does not establish a concrete malicious attack; warn rather than block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package in a project that depends on @lystech/core, unless setup is skipped or the workflow already exists.
Impact
A repository integration is added without affirmative setup consent during installation, and repository metadata may be sent when the workflow runs.
Mechanism
The hook writes .github/workflows/sync-package-registry.yml; the generated workflow later contacts the registry endpoint on pushes or manual dispatch.
AI rationale
Source confirms an automatic install hook that writes a repository workflow and a later registry interaction. This is a real install-time capability with an opt-out, but the inspected source does not establish a concrete malicious attack; warn rather than block.
Evidence
package.jsonbin/postinstall.cjs.github/workflows/sync-package-registry.yml
Network endpoints1
lysbunback-usgg4.ondigitalocean.app/api/package-registry
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.cjs automatically after installation.
- The hook writes .github/workflows/sync-package-registry.yml into a consuming project when @lystech/core is a dependency and the workflow is absent.
- The generated workflow sends repository owner, name, and ID to lysbunback-usgg4.ondigitalocean.app and can later request registry removal.
- The hook supports SKIP_LYSTECH_SETUP=true, but setup proceeds by default.
Evidence against
- The hook skips execution when the current project's package name is @lystech/core.
- The generated workflow performs registry actions on later GitHub pushes or manual dispatch; the install hook itself writes the workflow.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedTelemetry
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
2 Critical7 High5 Medium6 Low
CriticalCredential Exfiltrationdist/lystech-core-provider.umd.js
CriticalTrigger Reachable Dangerous Capabilitydist/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
HighKnown Malware Source Fingerprint Signaturebin/attach.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
Medium
Affected versions and remediation
This report applies to @lystech/core@3.0.140.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.140 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.