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.
module-lens
Advanced tools
yarn add module-lens
import {resolve} from 'module-lens';
let path = resolve('foo/bar', {
sourceFileName: __filename,
baseUrlDirName: __dirname,
});
console.log(path);
let specifier = build(path, {
sourceFileName: __filename,
baseUrlDirName: __dirname,
});
console.log(specifier);
The popular module resolving package resolve resolves a module specifier to a file, and throws an error if not being able to resolve to the final entry point. The resolve
of Module Lens, however, does only minimal checks to determine where should the specifier be resolved to.
Module Lens resolve
does not resolve a specifier to the final entry point, for example:
// if we have module "rxjs" installed:
resolve('rxjs/not-exists', {sourceFileName: __filename}); // -> 'node_modules/rxjs/not-exists'
MIT License.
FAQs
Simple module specifier utilities.
The npm package module-lens receives a total of 5 weekly downloads. As such, module-lens popularity was classified as not popular.
We found that module-lens 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.