npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

private-key-recovery

v1.4.1

Published

Private key recovery script to brute-force broken private keys in WIF.

Downloads

24

Readme

private-key-recovery

Build Status dependencies License: MIT

Description

Recovers a broken private key that misses up to 5 characters within one hour or faster. It brute forces its way until the checksum (base58check) is correct for the private key (thus having found the original key). Make sure to place '?' at places where the characters are unknown. Currently only 52 character WIF keys are supported. It could find 6 missing characters, though this would take approximately one day.

Installation

yarn add private-key-recovery 
npm i private-key-recovery

Import it:

var { recover } = require('private-key-recovery')

Usage

You can do

// question marks throughout the key
recover('KwNryX9f7W?jXNPjn?aefBoh?wG9GPK6Y7Vh?JKSwsxL8oy5T?q1') 

// or e.g. all question marks next to each other
recover('wNryX9f7WSjXNPjnsaefBohLwG9GPK6Y7VhvJKSwsxL8oy?????')  

The recovered private key will show up in your logs and it will be the return value of the function recover.

The function recover takes additional arguments. You can tell it how frequently it should log to the console (2nd argument, number) and on what number it should start with iterating (3rd argument, number).

The order of base58 that is implemented in this module is 123456789abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ

So it starts at 1 and it ends on Z.

Logging

Every 100.000 iterations an update is sent to the console. You can pass a numeric value as the second argument to change this.

License

MIT © Guus Baggen