@upsnap/strapi
Complete website health monitoring for Strapi, including uptime, SSL certificates, broken links, performance metrics, domain health, and mixed content issues.
This report shows the evidence for @upsnap/strapi@1.0.16, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package implements a concrete automatic collection-and-exfiltration chain for administrator PII and deployment metadata unrelated to a user-invoked monitoring action. The lack of install hooks does not remove this runtime data-exfiltration behavior.
Decision evidence
public snapshot- Admin initializer automatically posts browser fingerprint data.
- Server queries first Strapi admin's email, name, phone, and company.
- Collected PII, site URL, IP/geolocation, and platform details are POSTed to Upsnap.
- No npm lifecycle hooks are declared.
- No shell execution, remote code loading, or destructive file operations found.
Source & flagged code
2 flagged · loading sourcePackage contains a possible secret pattern.
dist/admin/App-Bmr3gqRi.mjsView on unpkg · L8667Hardcoded password in dist/admin/App-Cr2OWnQL.js
dist/admin/App-Cr2OWnQL.jsView on unpkg · L8673Findings
Affected versions and remediation
This report applies to @upsnap/strapi@1.0.16.
The versions list below shows the verdict for each recorded version.
- Avoid installing @upsnap/strapi@1.0.16. 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.