@zortexhq/install@0.1.48
Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Zortex Windows Codex bootstrap
AI Security Review
scanned 2h ago · by lpm-firewall-aiSource inspection confirms that ordinary Google grant refresh can send a saved refresh token to a package-selected broker without recipient-specific consent. This is concrete credential exfiltration behavior.
Decision evidence
public snapshot- The package exposes the `zortex` command through `bin/zortex.js`.
- The launcher starts the packaged runtime bundle.
- Without a configured OAuth client secret, the Google refresh helper selects the Zortex OAuth broker and puts the saved refresh token in the request body.
- The helper sends that body in a POST request.
- Google refresh is wired into grant refresh and startup processing.
Source & flagged code
10 flagged · loading sourcePackage contains a possible secret pattern.
dist/netease-imap-snapshot.tsView on unpkg · L27Package source references weak cryptographic algorithms.
dist/netease-imap-snapshot.tsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @zortexhq/install@0.1.48.
See all versions of @zortexhq/install for other recorded verdicts.
- Avoid installing @zortexhq/install@0.1.48. 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.