@lystech/core@3.0.141
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 3h ago · by lpm-firewall-aiSource confirms an install-time hook that automatically writes a CI workflow and configures repository registration with the package service. This is a real installation-time mutation, but the inspected behavior is package-aligned and does not establish a concrete malicious attack, so 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 consumer project that declares @lystech/core, unless SKIP_LYSTECH_SETUP=true is set.
Impact
Consumer repositories receive an unrequested CI workflow and disclose repository metadata to the registry service; the workflow also has a path to delete that repository’s registry entry.
Mechanism
The hook writes .github/workflows/sync-package-registry.yml; that workflow runs on pushes and posts repository information to the package registry service.
AI rationale
Source confirms an install-time hook that automatically writes a CI workflow and configures repository registration with the package service. This is a real installation-time mutation, but the inspected behavior is package-aligned and does not establish a concrete malicious attack, so 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 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.cjs during installation.
- The postinstall checks whether the consumer declares @lystech/core, then writes a GitHub Actions workflow automatically.
- That workflow sends repository information to the package registry service on pushes and can delete the registry entry when the package is absent.
Evidence against
- The workflow is limited to repositories that declare @lystech/core, and the hook can be skipped with SKIP_LYSTECH_SETUP=true.
- The inspected behavior appears intended to support this package’s update and registry features; it does not establish credential theft or destructive activity.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedTelemetryUrlStrings
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.141.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.141 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.