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.
[![Current Version](https://img.shields.io/npm/v/rjsvm.svg)](https://www.npmjs.com/package/rjsvm) [![Weekly Downloads](https://img.shields.io/npm/dw/rjsvm?color=important)](https://www.npmjs.com/package/rjsvm) [![License Type](https://img.shields.io/npm/l
The Ripple JavaScript Virtual Machine, or RJSVM, aims to standardize and simplify the development of applications that employ the Ripple blockchain as state storage. Internally it employs xrpIO to read and write all necessary data.
npm i rjsvm
The JSVM package comes with two major parts: The RJSVM itself and the Datawriter. The former is used to define initial program state, callable endpoints, and the associated their associated logic. The Datawriter serves as the glue between users and a RJSVM.
Due to the blockchain's properties of providing persistent and absolutely ordered transactions every copy of a RJSVM will behave exactly identically.
In order to provide a more robust environment and quasi-typesafe execution this package also requires zod.
RJSVM
import { RJSVM_Builder, RJSVM_Implementations, RJSVM_Interface, RJSVM, RJSVM_Config } from "rjsvm";
import { z } from "zod";
// Begin by defining the parameter type using Zod
const blogpostSchema = z.object({
title: z.string(),
body: z.string(),
from: z.string(),
})
type Blogpost = z.infer<typeof blogpostSchema>
// Define the shape of the state the RJSVM will manipulate
type State = {
data: Blogpost[]
}
// Define the RJSVM endpoints
type RJSVMEndpoints = {
submit: (data: Blogpost) => void
ownerSubmit: (data: Blogpost) => void
remove: (data: Blogpost) => void
}
// Define initial RJSVM state. The 'owner' and 'state' fields are both required.
abstract class RJSVM_Base
extends RJSVM<State, RJSVMEndpoints>
implements RJSVM_Interface<RJSVM_Base> {
owner = ownerWallet.address
state: State = {
blogposts: []
}
}
// Implement the program logic
const RJSVM_Contract: RJSVM_Implementations<RJSVM_Base> = {
// Endpoints may declare a minimum fee in order to be applied
submit: {
implementation: function (env, data) {
this.state.blogposts.unshift(data)
},
visibility: 'public',
fee: 10,
parameterSchema: blogpostSchema
},
// Endpoints can be owner-exclusive in order to grant free access
ownerSubmit: {
implementation: function (env, shout) {
this.state.blogposts.unshift(shout)
},
visibility: 'owner',
parameterSchema: blogpostSchema
},
// Owner-exclusive endpoints can also be used to implement protected functionality
remove: {
implementation: function (env, data) {
this.state.blogposts = this.state.blogposts.filter(post => post.title != post.title)
},
visibility: 'owner',
parameterSchema: blogpostSchema,
}
}
// Finally build and connect the RJSVM
const Rjsvm = RJSVM_Builder.from(RJSVM_Base, RJSVM_Contract);
const conf: RJSVM_Config = {
listeningAddress: listeningWallet.address, // The XRP address to check for endpoint calls
rippleNode: "wss://s.altnet.rippletest.net:51233" // Any online XRP node connected to the right chain
}
const rjsvm = new Rjsvm(conf)
rjsvm.connect()
Datawriter
import { Datawriter } from "rjsvm";
const datawriter = new Datawriter({
sendWallet: userWallet, // A wallet controlled by the user
receiveAddress: drainWallet.address, // A secondary address controlled by the user
xrpNode: xrpNode, // Any online XRP node connected to the right chain
contractAddress: listeningWallet.address // The XRP associated with the RJSVM
})
datawriter.callEndpoint('submit', {
title: "My first blogpost",
body: "Hello hello this is a blogpost!",
from: "#1 RJSVM User in the world"
}, 10)
// once the ripple blockchain persists the transaction, all copies of the RJSVM defined above will contain this blogpost
datawriter.callEndpoint('submit', {
title: "A underfunded blogpost",
body: "Oh no this will never show up!",
from: "#1 RJSVM User in the world"
})
// Insufficient fee, the RJSVMs will not contain this blogpost. No refunds.
datawriter.ownerSubmit('ownerSubmit', {
title: "A underprivileged blogpost",
body: "Oh no this will never show up!",
from: "#1 RJSVM User in the world"
})
// userWallet.address != ownerWallet.address, the RJSVMs will not contain this blogpost.
FAQs
[![Current Version](https://img.shields.io/npm/v/rjsvm.svg)](https://www.npmjs.com/package/rjsvm) [![Weekly Downloads](https://img.shields.io/npm/dw/rjsvm?color=important)](https://www.npmjs.com/package/rjsvm) [![License Type](https://img.shields.io/npm/l
The npm package rjsvm receives a total of 0 weekly downloads. As such, rjsvm popularity was classified as not popular.
We found that rjsvm 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.