registry / Data exfiltration / @lystech/core
@lystech/core
Lystech Core contains essentials for lystech apps
This report shows the evidence for @lystech/core@3.0.126. 17 of 53 known versions are blocked or flagged. The newest version, 3.0.141, is flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe postinstall hook installs a workflow that later discloses consumer repository identifiers to a publisher-selected endpoint without affirmative consent. This is an automatic installation disclosure, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package in a project whose manifest includes @lystech/core, followed by a push to the configured branch.
Impact
Consumer repository identity is disclosed without an affirmative setup action, and the added workflow continues to run on later pushes.
Mechanism
The hook writes a workflow into .github/workflows; the workflow retrieves the repository ID from GitHub and posts it with the owner, repository name, and package name to the publisher endpoint.
Attack narrative
During installation, the package automatically creates a GitHub workflow in the consumer project. On later pushes, that workflow sends the repository owner, name, and ID to the publisher’s registry endpoint. The hook offers an environment-variable skip, but does not require affirmative consent before creating the workflow.
AI rationale
The postinstall hook installs a workflow that later discloses consumer repository identifiers to a publisher-selected endpoint without affirmative consent. This is an automatic installation disclosure, so the package should be blocked.
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 Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs bin/postinstall.cjs automatically during installation.
- The hook checks the consumer manifest and creates a workflow under .github/workflows when the package is present.
- The generated workflow queries GitHub for the repository ID, then sends the package name, repository owner, name, and ID to the publisher endpoint on push.
- The postinstall hook has a skip environment variable, but otherwise creates the workflow without an affirmative consent step.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
9 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
3// Script universel de vérification PWA pour un projet Node.js (CommonJS)
L4: const fs = require("fs");
L5: const path = require("path");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/check-pwa.cjsView on unpkg · L3Findings
2 Critical5 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/postinstall.cjs
HighKnown Malware Source Similaritybin/setup-registry.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/check-pwa.cjs
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to @lystech/core@3.0.126.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lystech/core@3.0.126. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.