@tachybase/module-cloud-component@1.6.54
Cloud component
AI Security Review
scanned 1d ago · by lpm-firewall-aiThis is a credential-forwarding vulnerability in the remote-library fetch flow, not evidence of deliberate package malware. It requires a configured and enabled remote library, so the appropriate verdict is suspicious with a warning.
Decision evidence
public snapshot- The remote fetcher adds the configured bearer token to the HTTP Authorization header.
- It follows redirects and passes the same authentication credentials to the redirect URL without checking its host, which can expose the token to a third party.
- At application startup, the service fetches remote code for enabled libraries when no cached code is available.
- Remote libraries are disabled by default, so this requires a library to be configured and enabled.
- The remote code fetch and execution support is part of the package’s cloud-library feature.
- The manifest has no install scripts and no runtime dependencies.
Source & flagged code
6 flaggedPackage source executes code through a VM context API.
dist/server/services/cloud-libraries-service.jsView on unpkg · L47Package contains source files above the normal full-analysis size ceiling.
dist/client/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @tachybase/module-cloud-component@1.6.54.
See all versions of @tachybase/module-cloud-component for other recorded verdicts.
- Review the evidence and your use of @tachybase/module-cloud-component@1.6.54 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.