Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Issue DNS lookups for Dat archives using HTTPS requests to the target host.
See hyper-dns for similar functionality.
More info on active projects and modules at dat-ecosystem.org
Issue DNS lookups for Dat archives using HTTPS requests to the target host. Keeps an in-memory cache of recent lookups.
var datDns = require('dat-dns')()
// or, if you have a custom protocol
var datDns = require('dat-dns')({
recordName: /* name of .well-known file */
protocolRegex: /* RegExp object for custom protocol */,
hashRegex: /* RegExp object for custom hash i.e. */,
txtRegex: /* RegExp object for DNS TXT record of custom protocol */,
})
// example:
var cabalDns = require('dat-dns')({
recordName: 'cabal',
hashRegex: /^[0-9a-f]{64}?$/i,
protocolRegex: /^cabal:\/\/([0-9a-f]{64})/i,
txtRegex: /^"?cabalkey=([0-9a-f]{64})"?$/i
})
// resolve a name: pass the hostname by itself
datDns.resolveName('foo.com', function (err, key) { ... })
datDns.resolveName('foo.com').then(key => ...)
// dont use cached 'misses'
datDns.resolveName('foo.com', {ignoreCachedMiss: true})
// dont use the cache at all
datDns.resolveName('foo.com', {ignoreCache: true})
// dont use dns-over-https
datDns.resolveName('foo.com', {noDnsOverHttps: true})
// dont use .well-known/dat
datDns.resolveName('foo.com', {noWellknownDat: true})
// list all entries in the cache
datDns.listCache()
// clear the cache
datDns.flushCache()
// configure the DNS-over-HTTPS host used
var datDns = require('dat-dns')({
dnsHost: 'dns.google.com',
dnsPath: '/resolve'
})
// use a persistent fallback cache
// (this is handy for persistent dns data when offline)
var datDns = require('dat-dns')({
persistentCache: {
read: async (name, err) => {
// try lookup
// if failed, you can throw the original error:
throw err
},
write: async (name, key, ttl) => {
// write to your cache
}
}
})
// emits some events, mainly useful for logging/debugging
datDns.on('resolved', ({method, name, key}) => {...})
datDns.on('failed', ({method, name, err}) => {...})
datDns.on('cache-flushed', () => {...})
Option 1 (DNS-over-HTTPS). Create a DNS TXT record witht he following schema:
datkey={key}
Option 2 (.well-known/dat). Place a file at /.well-known/dat
with the following schema:
{dat-url}
TTL={time in seconds}
TTL is optional and will default to 3600
(one hour). If set to 0
, the entry is not cached.
FAQs
Issue DNS lookups for Dat archives using HTTPS requests to the target host.
The npm package dat-dns receives a total of 99 weekly downloads. As such, dat-dns popularity was classified as not popular.
We found that dat-dns demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 12 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.