@retailrocketgroup/retailrocket-edit.abandoned-search-vue-email-template-render@11.0.433360
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe packaged editor points its reset form at an unrelated webhook collector and submits the anti-forgery token there. The scaffold's token fields are placeholders and the submission requires a UI action, so the source supports a serious risk but does not establish active credential theft.
Decision evidence
public snapshot- The built HTML directs the reset form to a unique webhook.site collector.
- The reset handler places the anti-forgery form token in a POST to the configured reset URL.
- The handler is triggered when returning to template selection, and the build uses the HTML containing the collector URL.
- The checked-in HTML supplies literal placeholder strings for the anti-forgery token fields, so this snapshot does not prove a real token is sent.
- The POST occurs in response to the editor's return-to-template-selection action, rather than automatically on import.
Source & flagged code
6 flaggedSource fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/assets/index.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
dist/assets/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @retailrocketgroup/retailrocket-edit.abandoned-search-vue-email-template-render@11.0.433360.
See all versions of @retailrocketgroup/retailrocket-edit.abandoned-search-vue-email-template-render for other recorded verdicts.
- Review the evidence and your use of @retailrocketgroup/retailrocket-edit.abandoned-search-vue-email-template-render@11.0.433360 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.