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.
@kyve/avalanche
Advanced tools
@kyve/avalanche
The official KYVE node for Avalanche.
The KYVE + Avalanche node allows you to bridge any data stream from an Avalanche chain onto Arweave.
There are two ways to run the node. You can either run the integration itself or run a prebuilt version of the KYVE Node.
import AvalancheInstance from "@kyve/avalanche";
const poolID = ...
const stake = ...
AvalancheInstance(poolID, stake, jwk).run();
The config is pool specific. You can find a list of pool here. For this integration the config should look like this:
{
"endpoint": "wss://...."
}
The Avalanche integration uses the websocket endpoint to listen to the latest block data. For more information have a look at their documentation.
FAQs
The official KYVE node for Avalanche
The npm package @kyve/avalanche receives a total of 0 weekly downloads. As such, @kyve/avalanche popularity was classified as not popular.
We found that @kyve/avalanche demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.