
Security News
/Research
Wallet-Draining npm Package Impersonates Nodemailer to Hijack Crypto Transactions
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
@spruceid/didkit-wasm-node
Advanced tools
[](https://www.npmjs.com/package/@spruceid/didkit-wasm) [ you will need the WASM compiler toolchain as well as a specific build tool:
$ rustup target add wasm32-unknown-unknown
$ cargo install wasm-pack
# OR
# $ curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh
WASM can be used in Node.js (any recent version):
$ npm i @spruceid/didkit-wasm-node
Or build it from source:
$ wasm-pack build --target nodejs
WASM can be used with web frameworks and bundlers like Webpack:
$ npm i @spruceid/didkit-wasm
Or build it from source:
$ wasm-pack build
If Webpack doesn't work with the default configuration, you can have a look at our configuration for tzprofiles.
WASM can be used with plain Javascript with newer browsers. As it cannot be used as a NPM package you have to build it manually:
$ wasm-pack build --target web
The manual tests in test/
serve as an example on how to import DIDKit.
The test/
directory contains manual tests to run in the browser. Instructions
are in the README of the directory.
The current version of the ring
crate does not provide all the symbols
needed to run on the browser, see DEPS.md
To compile all features plus wasm32_c
on ring
, a C compiler is needed, see
spruceid/ssi:
On Ubuntu this one option is to install clang
and llvm
:
sudo apt install clang-10 llvm-10
Then to compile with all features:
TARGET_CC=clang-10 TARGET_AR=llvm-ar-10 wasm-pack build --out-dir pkg
To use a custom subset of features:
wasm-pack build --out-dir pkg -- --no-default-features --features=issue # issue credential/presentation
wasm-pack build --out-dir pkg -- --no-default-features --features=verify # verify credential/presentation
wasm-pack build --out-dir pkg -- --no-default-features --features=credential # issue/verify credential
wasm-pack build --out-dir pkg -- --no-default-features --features=presentation # issue/verify presentation
don't forget to add TARGET_CC
and TARGET_AR
if using ring
with wasm32_c
FAQs
[](https://www.npmjs.com/package/@spruceid/didkit-wasm) [![](https://img.shields.io/npm/v/@spruceid/didkit-wasm-node?label=%40spruceid%2Fdidkit-wasm-node&logo=
The npm package @spruceid/didkit-wasm-node receives a total of 447 weekly downloads. As such, @spruceid/didkit-wasm-node popularity was classified as not popular.
We found that @spruceid/didkit-wasm-node demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 6 open source maintainers 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.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.