#ganon551-card-testing
1 messages · Page 1 of 1 (latest)
Hi, you mean one of the successfull payments id ?
I have the logs from developper dashboard too
pm_1LDh9fEWxG45zMzrgDtjeZnR
I calmed down the attack by deleting these checkout buttons but since this morning it's getting back and I get several test per minutes again
pi_3LDgVQEWxG45zMzr0bW2ZGsr_secret_jerM4ZJ2m72TVRQ08hbGiyNZe
oups not this one sorry
this one :
"id": "pi_3LDgVQEWxG45zMzr0bW2ZGsr"
payment intent
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
this created the Checkout Session that the attacker is trying to confirm
it's from your server, Node
You would want to check which endpoint trigger this call
can disable that endpoint, or the button trigger request to that endpoint
How could I do that ? I don't know where they found a checkout access on the website, there's nothing left
You have your code right? where do you create a Checkout Session?
I have all my pages opened in visual studio, a search for "stripe" doesn't show me any node code that would make a call to checkout
here's a "out of session " payment
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
They are all comes from Checkout Session. Each Session has 24 hours active so the attacker could still use them
- Revoke every endpoint that created the Checkout Session
- Expire every currently active Checkout Session
For 1 I believe you already did it, but you may want to double check your backend, the code where you created Session
for 2, you can use the List Session API https://stripe.com/docs/api/checkout/sessions/list then loop through the result, call Expire Session API https://stripe.com/docs/api/checkout/sessions/expire
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
For 1, I did remove all buttons that lead to Stripe checkout, and removed all the nodeJS code that has to do with Stripe on the main-site. In the backend there's still the JS codes to create sessions but they cannot access it
I'll check the later
Ok I made a request using curl
Using some script/code would be easier, as you would likely need to loop through the result
I'm looking at timestamps
The first visit date for one of them for instance was 21/06/2022 16:53:53 and the expiration date is 23/06/2022 21:00:48
I will end all of them
Looks like all the sessions were marked as "null"
Well, no subscriptions since an hour so will see if it continues
You agree that if every trace of stripe js code, buttons, etc are removed from the main public site they shouldn't be able to access checkout right ?
you can also consider rolling both your secret and publishable key to be extra safe