@lystech/core@3.0.139
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe postinstall hook automatically changes consumer CI configuration, while the generated workflow later sends repository identifiers to the publisher. Its package-related purpose and the need for a later workflow run reduce the risk, but the automatic configuration change warrants a warning.
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 lists it as a dependency, unless the opt-out is set or the workflow already exists; later disclosure requires running the generated workflow.
Impact
Consumer CI configuration is changed automatically, and a later workflow run discloses repository identity. The source does not establish credential theft or arbitrary code execution.
Mechanism
The postinstall hook writes a GitHub Actions workflow. That workflow obtains the repository ID from GitHub and posts it with the repository owner, name, and package name to the publisher’s registry endpoint.
AI rationale
The postinstall hook automatically changes consumer CI configuration, while the generated workflow later sends repository identifiers to the publisher. Its package-related purpose and the need for a later workflow run reduce the risk, but the automatic configuration change warrants a warning.
Evidence
package.jsonbin/postinstall.cjs.github/workflows/sync-package-registry.yml
Network endpoints2
api.github.com/repos/$OWNER/$REPO_NAMElysbunback-usgg4.ondigitalocean.app/api/package-registry
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs the postinstall hook automatically.
- The hook skips only when the opt-out is set, or when its package checks or existing-workflow check cause an exit.
- The hook creates a workflow that runs on pushes to main or master and can also be started manually.
- The workflow sends the package name, repository owner, name, and ID to the publisher’s registry endpoint.
- The repository ID is looked up through GitHub using the workflow token.
- The hook prints instructions to commit and push the generated workflow before its push trigger runs.
Evidence against
- The registry request is deferred until the generated workflow runs; the hook itself does not send repository data over the network.
- The workflow is package-related and its registry sync requires the consumer to commit and push the generated file or start it manually.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.139.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.139 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.