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.
extendable-media-recorder
Advanced tools
An extendable drop-in replacement for the native MediaRecorder.
An extendable drop-in replacement for the native MediaRecorder.
This package provides (a part of) the MediaRecorder API as defined by the MediaStream Recording specification. If possible it will use the native implementation.
In addition this package also allows to define custom encoders. Those encoders can be used to render files which are not supported by any browser so far. This does currently only work for audio encoders.
extendable-media-recorder
is available on npm and can be installed as usual.
npm install extendable-media-recorder
It exports the MediaRecorder
constructor. It can be used like the native implementation. The following example will use the default encoder that is defined by the browser.
import { MediaRecorder } from 'extendable-media-recorder';
const stream = await navigator.mediaDevices.getUserMedia({ audio: true });
const mediaRecorder = new MediaRecorder(stream);
extendable-media-recorder
also exports a register()
function which can be used to define custom encoders. One predefined encoder is available as the extendable-media-recorder-wav-encoder
package. It can be used as shown here.
import { MediaRecorder, register } from 'extendable-media-recorder';
import { connect } from 'extendable-media-recorder-wav-encoder';
await register(await connect());
const stream = await navigator.mediaDevices.getUserMedia({ audio: true });
const mediaRecorder = new MediaRecorder(stream, { mimeType: 'audio/wav' });
The MediaRecoder
has no way to modify the sample rate directly. It uses the sampleRate
of the given MediaStream
. You can read the value being used like this:
const { sampleRate } = stream.getAudioTracks()[0].getSettings();
To modifiy the sample rate of the recording you need to change the sampleRate
of the MediaStream
. But that's not possible either. Therefore the most reliable way is to use an AudioContext
at the desired sampleRate
to do the resampling.
const audioContext = new AudioContext({ sampleRate: 16000 });
const mediaStreamAudioSourceNode = new MediaStreamAudioSourceNode(audioContext, { mediaStream: stream });
const mediaStreamAudioDestinationNode = new MediaStreamAudioDestinationNode(audioContext);
mediaStreamAudioSourceNode.connect(mediaStreamAudioDestinationNode);
const mediaRecorder = new MediaRecorder(mediaStreamAudioDestinationNode.stream);
Internally two different techniques are used to enable custom encoders. In Chrome the native MediaRecorder is used to encode the stream as webm file with pcm encoded audio. Then a minimal version of ts-ebml is used to parse that pcm data to pass it on to the encoder. In other browsers the Web Audio API is used to get the pcm data of the recorded audio.
FAQs
An extendable drop-in replacement for the native MediaRecorder.
The npm package extendable-media-recorder receives a total of 33,328 weekly downloads. As such, extendable-media-recorder popularity was classified as popular.
We found that extendable-media-recorder demonstrated a healthy version release cadence and project activity because the last version was released less than 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.