Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
This is a NodeJS module for processing navigator.mozPay() payments on a server.
You'll need to obtain a secret key from a provider such as the Firefox Marketplace but this module should work with any compliant provider. Here is a guide to setting up payments with Firefox Marketplace.
The basic payment flow goes like this:
navigator.mozPay()
npm install mozpay
The module is intended to be used server side only because you can't expose your secret key to the client. There are helpers to hook into an express app but you could probably use other web frameworks too.
Load the module:
var pay = require('mozpay');
Configure it when your app starts up:
pay.configure({
// This is your Application Key from the Firefox Marketplace Devhub.
mozPayKey: '52ee5d47-9981-40ad-bf6e-bca957f65385',
// This is your Application Secret from the Firefox Marketplace Devhub.
mozPaySecret: 'd6338705419ea14328084e0c182603ebec4e52c1c6cbceda4d61ee125f10c0f728c4451a4637e4e960b3293df8bb6ac5',
// This is the aud (audience) in the JWT. You only need to override this if you want to use a dev server.
mozPayAudience: 'marketplace.firefox.com',
// This is an optional prefix to your postback/chargeback URLs.
// For example, a postback would be available at https://yourapp/mozpay/postback with the default prefix.
mozPayRoutePrefix: '/mozpay',
// Set a custom payment type for JWTs. You only need to override this if
// you're working with a non-default payment provider.
mozPayType: 'mozilla/payments/pay/v1',
// This is an optional list of JWT algorithms to support when verifying
// messages from the Firefox Markeplace. It defaults to HS256 only since
// that's what the Marketplace uses.
supportedAlgorithms: ['HS256'],
});
With an express 4 app object, add your routes:
var express = require('express');
var bodyParser = require('body-parser');
var pay = require('mozpay');
var app = express();
app.configure(function(){
// Make sure you turn on the body parser for POST params.
app.use(express.bodyParser());
});
app.use(bodyParser.urlencoded({ extended: false }));
app.use(bodyParser.json());
pay.routes(app);
You can test your postback/chargeback URLs with something like this:
curl -X POST -d notice=JWT http://localhost:3000/mozpay/postback
curl -X POST -d notice=JWT http://localhost:3000/mozpay/chargeback
If you see a 400 Bad Request response then your app is configured to receive real JWT requests.
You can combine the configuration and routes setup like this:
pay.routes(app, {
mozPayKey: '52ee5d47-9981-40ad-bf6e-bca957f65385',
mozPaySecret: 'd6338705419ea14328084e0c182603ebec4e52c1c6cbceda4d61ee125f10c0f728c4451a4637e4e960b3293df8bb6ac5',
// ...
});
Here's how to take action when the postback notices are
received. The data
argument to these event handlers are only for valid JWT
notices that pass the signature verification.
pay.on('postback', function(data) {
console.log('product ID ' + data.request.id + ' has been purchased');
console.log('Transaction ID: ' + data.response.transactionID);
});
pay.on('chargeback', function(data) {
console.log('product ID ' + data.request.id + ' failed');
console.log('reason: ' + data.response.reason);
console.log('Transaction ID: ' + data.response.transactionID);
});
The data.request
object is a copy of what you initiated the payment request
with.
When a user clicks the buy button you should fetch a JWT from the server via Ajax. You can't cache JWTs for too long because they have a short expiration (generally about an hour).
There is a helper to created a JWT to begin a payment. On your server create a URL that does something like this:
var jwt = pay.request({
id: 'your-unique-product-id',
name: 'Your Product',
description: 'A little bit more about the product...',
pricePoint: 1, // Consult the Firefox Marketplace price points for details.
// This expands to a price/currency at the time of payment.
productData: 'session_id=xyz', // You can track whatever you like here.
// These must be absolute URLs like what you configured above.
postbackURL: 'http://localhost:3000/mozpay/postback',
chargebackURL: 'http://localhost:3000/mozpay/chargeback'
});
In your client-side JavaScript, you can initiate a payment with the JWT like this:
var request = navigator.mozPay([jwtFromServer]);
request.onsuccess = function() {
console.log('navigator.mozPay() finished');
// The product has not yet been bought!
// Poll your server until a valid postback has been received.
waitForPostback();
}
request.onerror = function() {
console.log('navigator.mozPay() error: ' + this.error.name);
};
Grab the source:
git clone git://github.com/mozilla/mozpay-js.git
Install the dependencies:
cd mozpay-js
npm install
Here's how to run the tests:
npm test
FAQs
fulfill web payments with navigator.mozPay()
The npm package mozpay receives a total of 0 weekly downloads. As such, mozpay popularity was classified as not popular.
We found that mozpay demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.