registry / Data exfiltration / @retailrocketgroup/retailrocket-edit.abandoned-view-vue-email-template-render
@retailrocketgroup/retailrocket-edit.abandoned-view-vue-email-template-render
This report shows the evidence for @retailrocketgroup/retailrocket-edit.abandoned-view-vue-email-template-render@11.0.433360. 3 of 13 known versions are blocked or flagged. The newest version, 11.0.433449, is allowed. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reset flow submits an anti-forgery token to a hard-coded external webhook collector. That unrelated token disclosure is concrete data exfiltration.
Static reason
No blocking static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
When the app invokes its return-to-template-selection handler.
Impact
The collector receives the anti-forgery token, which could enable unauthorized actions against the user’s session.
Mechanism
It appends the token to a POST form whose destination is hard-coded in the built page as a webhook.site URL, then submits the form.
Attack narrative
When the app returns to template selection, it builds and submits a POST form containing the anti-forgery token. The published page points that form at a webhook.site collector, sending the token outside the RetailRocket service.
AI rationale
The reset flow submits an anti-forgery token to a hard-coded external webhook collector. That unrelated token disclosure is concrete data exfiltration.
Evidence
src/editAbandonedViewEmailTemplate.tsdist/index.html
Network endpoints3
webhook.site/a85a171c-bb86-4693-9552-d209a59a7e6amy.retailrocket.ruk8s-b1.retailrocket.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The reset handler puts the anti-forgery form token into a POST form and submits it to the configured reset URL.
- The built page configures that reset URL as a specific webhook.site collector.
Evidence against
- The editor’s save client sends requests to the configured template-editor BFF.
Behavioral surface
Network
HighEntropyStringsMinifiedTelemetryUrlStrings
NoLicense
Oversized source lightweight scan
dist/assets/index.js7.94 MB file, sampled 256 KB
NetworkHighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
6 flaggeddist/assets/index.jsView file
•matchType = malicious_source_fingerprint_signature
signature = a49f8411e2470f3f
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @retailrocketgroup/retailrocket-edit.abandoned-category-vue-email-template-render@11.0.433360
matchedPath = dist/assets/index.js
matchedIdentity = npm:[redacted]:11.0.433360
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 = 8324325
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
dist/assets/index.jsView on unpkgsrc/editAbandonedViewEmailTemplate.tsView file
Findings
5 High3 Medium4 Low
HighKnown Malware Source Fingerprint Signaturedist/assets/index.js
HighAi Review Evidencesrc/editAbandonedViewEmailTemplate.ts
HighAi Review Evidencesrc/editAbandonedViewEmailTemplate.ts
HighAi Review Evidencedist/index.html
HighAi Review Evidencesrc/editAbandonedViewEmailTemplate.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.abandoned-view-vue-email-template-render@11.0.433360.
The versions list below shows the verdict for each recorded version.
- Avoid installing @retailrocketgroup/retailrocket-edit.abandoned-view-vue-email-template-render@11.0.433360. 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.