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.
A wrapper for the Kashflow SOAP/WSDL API, using node-soap
Simplifies the process of creating a Kashflow client by adding Authentication to each call. Methods return Promises.
$ npm install --save kashflow
The library returns a Promise
which resolves with a kashflow
client object, which has Kashflow methods as its properties.
See the docs for available Kashflow methods.
const Kashflow = require('kashflow')
const { KASHFLOW_USERNAME, KASHFLOW_API_PASSWORD } = process.env
// Set up the client
Kashflow(KASHFLOW_USERNAME, KASHFLOW_API_PASSWORD).then(kashflow => {
// call methods on the client
return kashflow.GetInvoiceById({
InvoiceID: '12345'
})
.then(res => {
console.log(res.GetInvoiceByIdResult)
})
})
You'll need to create a .env
file in your project root as follows
KASHFLOW_USERNAME=<Your Username>
KASHFLOW_API_PASSWORD=<Your Password>
Then
npm test
FAQs
Wrapper for Kashflow SOAP API
We found that kashflow demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.