@lystech/core@3.0.100
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe postinstall automatically adds ongoing CI behavior and sends repository metadata to the package registry, creating unresolved install-time mutation risk. The inspected code does not establish credential exfiltration or another block-eligible attack, so a warning is appropriate.
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 depends on it, with no existing workflow and without the skip condition.
Impact
This silently adds ongoing CI behavior and shares repository identity metadata with the package service; inspected source does not establish credential theft or destructive behavior.
Mechanism
The hook creates .github/workflows/sync-package-registry.yml; its push-triggered workflow registers or removes repository metadata at the registry endpoint.
AI rationale
The postinstall automatically adds ongoing CI behavior and sends repository metadata to the package registry, creating unresolved install-time mutation risk. The inspected code does not establish credential exfiltration or another block-eligible attack, so a warning is appropriate.
Evidence
package.jsonbin/postinstall.cjs.github/workflows/sync-package-registry.yml
Network endpoints2
lysbunback-usgg4.ondigitalocean.app/api/package-registryapi.lystech.ca/api/
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package postinstall hook runs automatically and invokes bin/postinstall.cjs.
- The hook writes a GitHub Actions workflow into the consuming project when the package is present in its dependencies and the workflow does not already exist.
- That workflow sends repository owner, name, and ID to the package registry endpoint on pushes; the inspected workflow does not send repository credentials.
- The bundled provider reads application tokens from localStorage for request headers, while its API base is fixed to api.lystech.ca.
Evidence against
- The postinstall skips when run in the package's own directory, when SKIP_LYSTECH_SETUP is true, or when the workflow already exists.
- The install hook does not harvest credentials; the workflow shares repository metadata with the package's registry service.
- The bundle's token handling is consistent with authenticated provider requests to its fixed service endpoint.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
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 unpkgdist/lystech-core-provider.umd.jsView file
16Trigger-reachable chain: manifest.main -> dist/lystech-core-provider.umd.js
L16: * LICENSE file in the root directory of this source tree.
L17: */var Pp;function TO(){return Pp||(Pp=1,process.env.NODE_ENV!=="production"&&function(){var e=O,t=Symbol.for("react.element"),n=Symbol.for("react.portal"),r=Symbol.for("react.fragm...
L18: `+ae+G}}var ie=!1,le;{var K=typeof WeakMap=="function"?WeakMap:Map;le=new K}function te(G,we){if(!G||ie)return"";{var Re=le.get(G);if(Re!==void 0)return Re}var Fe;ie=!0;var nt=Erro...
...
L20: `),xt=ut.length-1,At=Ht.length-1;xt>=1&&At>=0&&ut[xt]!==Ht[At];)At--;for(;xt>=1&&At>=0;xt--,At--)if(ut[xt]!==Ht[At]){if(xt!==1||At!==1)do if(xt--,At--,At<0||ut[xt]!==Ht[At]){var Ue...
L21: `+ut[xt].replace(" at new "," at ");return G.displayName&&Ue.includes("<anonymous>")&
Findings
3 Critical7 High4 Medium5 Low
CriticalCredential Exfiltrationdist/lystech-core-provider.es.js
CriticalTrigger Reachable Dangerous Capabilitydist/lystech-core-provider.umd.js
CriticalPrevious Version Dangerous Deltabin/check-pwa.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretdist/lystech-core-provider.umd.js
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
HighSecret Patterndist/lystech-core-provider.umd.js
Medium
Affected versions and remediation
This report applies to @lystech/core@3.0.100.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.100 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.