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.
@wrote/read
Advanced tools
@wrote/read
is a package to read a file as a string or a Buffer.
yarn add -E @wrote/read
The package is available by importing its default function read
, and named function readBuffer
:
import read, { readBuffer } from '@wrote/read'
async read(
path: string,
): string
Read the file as a string.
/* yarn example/ */
import read from '@wrote/read'
(async () => {
const res = await read('example/data.txt')
console.log(res)
})()
Hello World
async readBuffer(
path: string,
): Buffer
Read the file as a Buffer.
/* yarn example/ */
import { readBuffer } from '@wrote/read'
(async () => {
const res = await readBuffer('example/data.txt')
console.log(res)
})()
<Buffer 48 65 6c 6c 6f 20 57 6f 72 6c 64>
© Art Deco for Wrote 2019 | Tech Nation Visa Sucks |
---|
FAQs
Read the contents of file from the filesystem.
The npm package @wrote/read receives a total of 31 weekly downloads. As such, @wrote/read popularity was classified as not popular.
We found that @wrote/read 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.