Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@devprotocol/dev-kit
Advanced tools
Dev Kit for JavaScript
First, install this repository as an npm package.
> npm i -D @devprotocol/dev-kit
You can use the Dev Protocol by importing it from a JavaScript(TypeScript) file.
import { contractFactory } from '@devprotocol/dev-kit'
import { providers } from 'ethers'
const provider = new providers.Web3Provider(window.ethereum)
const factory = contractFactory(provider)
const balance = await factory
.dev()
.balanceOf('0xB204f0Bb68De735b98abBA5ccAE7459837c2f084')
This is an example of retrieving the balance of the DEV token held by 0xB204f0Bb68De735b98abBA5ccAE7459837c2f084
It covers all the contracts and their functions that can be executed with the Dev Protocol.
The URL of the provider is easy to use with each node provisioning service.
## install dependency
> yarn
## test
> yarn test
## test with coverage
> yarn test:coverage
## build
> yarn build
FAQs
Dev Kit for JavaScript
We found that @devprotocol/dev-kit demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.