registry / @lystech/core / 3.0.132
@lystech/core@3.0.132
⚠ Under reviewLystech Core contains essentials for lystech apps
AI Security Review
scanned 1d ago · by lpm-firewall-aiInspected source does not establish active malicious behavior: the postinstall hook exits for this package, and the token-sync helper requires an explicit setting. Some declared runtime dependency source remains unresolved, so a clean verdict is not supported.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The declared postinstall hook runs during package installation, but its source exits when the package name is @lystech/core.
Impact
No confirmed attack impact was established; unresolved dependency source prevents a clean determination.
Mechanism
The hook contains code to create a registry-sync workflow after its guards. The bundle also contains an optional Firebase token-sync helper that requires an authTokenSyncURL setting.
AI rationale
Inspected source does not establish active malicious behavior: the postinstall hook exits for this package, and the token-sync helper requires an explicit setting. Some declared runtime dependency source remains unresolved, so a clean verdict is not supported.
Evidence
package.jsonbin/postinstall.cjsdist/lystech-core-provider.es.js
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares a postinstall hook, and the hook exits when it reads this package’s own name before reaching its workflow write.
- The hook writes a consumer workflow only after its earlier checks; the workflow contacts GitHub and a Lystech registry service.
- The bundled Firebase helper sends an ID token only when an authTokenSyncURL setting is present; no fixed recipient for that helper was identified.
- The bundled API client defaults to the Lystech API host, consistent with this package’s stated purpose.
- The manifest declares Firebase and other runtime dependencies, but source inspection for some dependency releases was unresolved.
Evidence against
- No confirmed credential theft, unrelated default recipient, or active attack was established in the inspected package source.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
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 = 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 Critical6 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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/check-pwa.cjs
MediumNetwork
Affected versions and remediation
This report applies to @lystech/core@3.0.132.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.132 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.