
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.
@dsnp/frequency-schemas
Advanced tools
Matching DSNP Version: v1.2.0
npm install @dsnp/frequency-schemas
import { dsnp } from "frequency-schemas";
console.log(dsnp.getSchema("broadcast"));
npm install @dsnp/parquetjs
import { parquet } from "frequency-schemas";
import { ParquetWriter } from "@dsnp/parquetjs";
const [parquetSchema, writerOptions] = parquet.fromFrequencySchema("broadcast");
const writer = await ParquetWriter.openFile(parquetSchema, "./file.parquet", writerOptions);
writer.appendRow({
announcementType: 2,
contentHash: "0x1234567890abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
fromId: 78187493520,
url: "https://spec.dsnp.org/DSNP/Types/Broadcast.html",
});
await writer.close();
npm install
npm run deploy
by default it will deploy to the localhost
node on port 9944 using the Alice sudo test account.
Two environment variables allow you to change these defaults:
DEPLOY_SCHEMA_ACCOUNT_URI="//Alice"
DEPLOY_SCHEMA_ENDPOINT_URL="ws://localhost:9944"
e.g.
DEPLOY_SCHEMA_ACCOUNT_URI="//Bob" DEPLOY_SCHEMA_ENDPOINT_URL="ws://127.0.0.1:9944" npm run deploy profile
e.g. To register the "profile" schema
npm run deploy profile
Note: Requires a sudo key if deploying to a testnet.
Mainnet will use the proposal system (proposeToCreateSchema
).
npm run deploy help
DEPLOY_SCHEMA_ENDPOINT_URL="ws://127.0.0.1:9944" npm run read
Will output various information about the schemas on the chain as well as attempt to match known DSNP schemas.
## Connection Information
┌─────────┬─────────────────────┬────────────────────────────────────────────┐
│ (index) │ key │ value │
├─────────┼─────────────────────┼────────────────────────────────────────────┤
│ 0 │ 'endpointUrl' │ 'wss://frequency-seal.liberti.social:9944' │
│ 1 │ 'clientVersion' │ '0.1.0-377bbe37fbe' │
│ 2 │ 'specName' │ 'frequency-rococo' │
│ 3 │ 'specVersion' │ '1' │
│ 4 │ 'latestBlockNumber' │ '16' │
└─────────┴─────────────────────┴────────────────────────────────────────────┘
## Schema Information
There are 8 schemas on the connected chain.
## Schema Id 1
┌─────────┬──────────────────────┬───────────────────────────────┐
│ (index) │ key │ value │
├─────────┼──────────────────────┼───────────────────────────────┤
│ 0 │ 'schema_id' │ '1' │
│ 1 │ 'model_type' │ 'Parquet' │
│ 2 │ 'payload_location' │ 'IPFS' │
│ 3 │ 'matchesDSNPSchemas' │ 'dsnp.broadcast,dsnp.profile' │
└─────────┴──────────────────────┴───────────────────────────────┘
## Schema Model
[
{
"name": "announcementType",
"column_type": {"INTEGER": {"bit_width": 32, "sign": true}},
"compression": "GZIP",
"bloom_filter": false
},
{
"name": "contentHash",
"column_type": "BYTE_ARRAY",
"compression": "GZIP",
"bloom_filter": true
},
{
"name": "fromId",
"column_type": {"INTEGER": {"bit_width": 64, "sign": false}},
"compression": "GZIP",
"bloom_filter": true
},
{
"name": "url",
"column_type": "STRING",
"compression": "GZIP",
"bloom_filter": false
}
]
...
This repo includes a docker image to push a Frequency instant-seal-node with the schemas deployed on top of it to docker hub under dsnp/instant-seal-node-with-deployed-schemas
.
For any local testing do the following:
docker pull dsnp/instant-seal-node-with-deployed-schemas:latest
docker run docker run --rm -p 9944:9944 -p 9933:9933 -p 30333:30333 dsnp/instant-seal-node-with-deployed-schemas:latest
docker build -t dsnp/instant-seal-node-with-deployed-schemas:latest -t dsnp/instant-seal-node-with-deployed-schemas:<versionNumberHere> .
To match with the Frequency version, a new tag should be pushed to update the docker version of this image each time frequency releases a new version. The following steps explain how to properly do a release for this.
git checkout main && git pull --rebase
git pull --tags
git tag docker/{insert version number}
. For example, if the version number is v1.0.0, then the tag should be docker/v1.0.0
Push the tag up: git push --tags
FAQs
Schemas for DSNP on Frequency
The npm package @dsnp/frequency-schemas receives a total of 13 weekly downloads. As such, @dsnp/frequency-schemas popularity was classified as not popular.
We found that @dsnp/frequency-schemas demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 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.