@retailrocketgroup/retailrocket-edit.abandoned-basket-price-drop-vue-email-template-render@11.0.433449
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe shipped reset flow sends a Retail Rocket anti-forgery token to a hard-coded webhook.site collector. This is credential exfiltration even though it is triggered by a UI action.
Decision evidence
public snapshot- The shipped dist/index.html sets the reset form destination to a unique webhook.site URL.
- The app reads that destination and the anti-forgery form token from HTML attributes, then submits the token in a POST form to the configured destination.
- Returning to template selection invokes the reset function, sending the token to the hard-coded webhook.
- The manifest has no lifecycle scripts, dependencies, or declared entry points.
- The token submission is triggered by the template-selection UI action rather than occurring during package installation.
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-basket-price-drop-vue-email-template-render@11.0.433449.
See all versions of @retailrocketgroup/retailrocket-edit.abandoned-basket-price-drop-vue-email-template-render for other recorded verdicts.
- Avoid installing @retailrocketgroup/retailrocket-edit.abandoned-basket-price-drop-vue-email-template-render@11.0.433449. 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.