registry / Credential exfiltration / @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render / 11.0.433123
@retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433123
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe built page points the reset form at an unrelated webhook.site URL, and the reset handler posts the anti-forgery token there. This is token exfiltration even though it is triggered by a UI action.
Static reason
No blocking static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The user selects the UI action to return to template selection.
Impact
The collector receives a token intended for the application’s own form flow, without the user being told it will be sent to that host.
Mechanism
The reset handler appends the anti-forgery form token to a form and submits it to the URL hardcoded in the built HTML.
Attack narrative
When the user returns to template selection, the application posts its anti-forgery form token to a hardcoded webhook.site collector instead of the application’s reset endpoint.
AI rationale
The built page points the reset form at an unrelated webhook.site URL, and the reset handler posts the anti-forgery token there. This is token exfiltration even though it is triggered by a UI action.
Evidence
dist/index.htmlsrc/editProductBackInStockEmailTemplate.ts
Network endpoints1
webhook.site
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The built HTML sets the reset form destination to a unique webhook.site URL.
- The reset handler adds the anti-forgery form token to a POST sent to that configured destination.
- The UI invokes the reset handler when the user returns to template selection.
Evidence against
- The token is sent only when the user chooses the return-to-template-selection action; no install scripts are declared.
Behavioral surface
Network
HighEntropyStringsMinifiedTelemetryUrlStrings
NoLicense
Oversized source lightweight scan
dist/assets/index.js7.94 MB file, sampled 256 KB
NetworkHighEntropyStrings
Source & flagged code
5 flaggeddist/assets/index.jsView file
•matchType = malicious_source_fingerprint_signature
signature = a49f8411e2470f3f
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @retailrocketgroup/retailrocket-edit.abandoned-view-vue-email-template-render@11.0.433123
matchedPath = dist/assets/index.js
matchedIdentity = npm:[redacted]:11.0.433123
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/assets/index.jsView on unpkg•path = dist/assets/index.js
kind = oversized_source_file
sizeBytes = 8323513
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
dist/assets/index.jsView on unpkgdist/index.htmlView file
Findings
4 High3 Medium4 Low
HighKnown Malware Source Fingerprint Signaturedist/assets/index.js
HighAi Review Evidencedist/index.html
HighAi Review Evidencesrc/editProductBackInStockEmailTemplate.ts
HighAi Review Evidencesrc/editProductBackInStockEmailTemplate.ts
MediumNetwork
MediumOversized Source Filedist/assets/index.js
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433123.
See all versions of @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render for other recorded verdicts.
- Avoid installing @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433123. 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.