paymob-integration

Warn

Audited by Socket on Nov 14, 2026

2 alerts found:

SecurityAnomaly
SecurityMEDIUM
SKILL.md

The payment-integration purpose and most data flows are coherent, with strong HMAC, secret-handling, and live-action safeguards. Risk is elevated by the unverified executable diagnostic ZIP, mutable third-party Pixel script, and explicit concealment of AI authorship. These are concerning but do not establish confirmed malware or credential theft.

Confidence: 91%Severity: 72%
AnomalyLOW
references/code-nodejs.md

This is readable payment-integration code, not apparent malware. The principal security concern is that merchant_order_id is used after HMAC verification despite not being included in the signed fields, creating a potential payment-to-order misattribution risk if the persistence adapter trusts it; associate payments using authenticated identifiers or validate the mapping server-side. The configured Paymob destination is accept[.]paymob[.]com, and the code uses PAYMOB_SECRET_KEY and PAYMOB_HMAC_SECRET; severity is medium pending review of the persistence adapter.

Confidence: 95%Severity: 55%
Audit Metadata
Analyzed At
Nov 14, 2026, 07:15 PM
Package URL
pkg:socket/skills-sh/paymobaccept%2Fpaymob-ai-integration-skill%2Fpaymob-integration%2F@38c765239758c0fb3f4568fe109744c55dc97fb956b59775c2e704f81bd470c1