
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
@crankk.io/chirpstack-api-fork
Advanced tools
ChirpStack gRPC API message and service wrappers for Javascript. Typescript definitions are included.
With npm:
npm install @chirpstack/chirpstack-api --save
Or with yarn:
yarn add @chirpstack/chirpstack-api
All messages, services, constants, etc. are auto-generated from the ChirpStack protobuf definitions. The result is that this package structure matches that of the protobuf definitions. There is no ES6 index gathering all of the exports, so full import/require paths should be used. The generated code is all callback based, but can be promisified.
The protobuf definitions can be found here: https://github.com/brocaar/chirpstack-api/tree/master/protobuf
The generated code all depends on the grpc
package, and for most use cases you will probably need to make use of the
grpc
package directly as well. This is seen in the example below.
This example shows how to log in to ChirpStack via the gRPC API and then create a gRPC metadata object containing the JWT. This metadata could then be passed to any future requests that require authorization.
import * as grpc from '@grpc/grpc-js';
import * as internalService from '@chirpstack/chirpstack-api/as/external/api/internal_grpc_pb';
import * as internalMessages from '@chirpstack/chirpstack-api/as/external/api/internal_pb';
// Create the client for the 'internal' service
const internalServiceClient = new internalService.InternalServiceClient(
'localhost:8080',
grpc.credentials.createInsecure()
);
// Create and build the login request message
const loginRequest = new internalMessages.LoginRequest();
loginRequest.setEmail('email');
loginRequest.setPassword('password');
// Send the login request
internalServiceClient.login(loginRequest, (error, response) => {
// Build a gRPC metadata object, setting the authorization key to the JWT we
// got back from logging in.
const metadata = new grpc.Metadata();
metadata.set('authorization', response.getJwt());
// This metadata can now be passed for requests to APIs that require authorization
// e.g.
// deviceServiceClient.create(createDeviceRequest, metadata, callback);
});
FAQs
Chirpstack JS and TS API
The npm package @crankk.io/chirpstack-api-fork receives a total of 0 weekly downloads. As such, @crankk.io/chirpstack-api-fork popularity was classified as not popular.
We found that @crankk.io/chirpstack-api-fork 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
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.