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.
include-path-searcher
Advanced tools
Helper functions for searching for files in multiple include paths
Utility functions for searching multiple include paths.
npm install --save include-path-searcher
var includePathSearcher = require('include-path-searcher')
includePathSearcher.findFileSync(relativePath, includePaths) // => fullPath
Searches for the file identified by relativePath
in any of the given
directories (includePaths
). Returns the full path of the first file found,
or throws an error if none found. For example:
includePathSearcher.findFileSync('foo.txt', ['dir1', 'dir2'])
This returns either 'dir1/foo.txt'
or 'dir2/foo.txt'
. If foo.txt
does
not exist in either directory, it throws an error.
FAQs
Helper functions for searching for files in multiple include paths
The npm package include-path-searcher receives a total of 68,820 weekly downloads. As such, include-path-searcher popularity was classified as popular.
We found that include-path-searcher 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.