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.
This package provides a drop-in alternative to subprocess.run
that
captures the output while still printing it in real-time, just the way
tee
does.
Printing output in real-time while still capturing is valuable for any tool that executes long-running child processes. For those, you do want to provide instant feedback (progress) related to what is happening.
# from subprocess import run
from subprocess_tee import run
result = run("echo 123")
result.stdout == "123\n"
You can add tee=False
to disable the tee functionality if you want, this
being a much shorter alternative than adding the well known
stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL
.
Keep in mind that universal_newlines=True
is implied as we expect text
processing, this being a divergence from the original subprocess.run
.
You can still use check=True
in order to make it raise CompletedProcess
exception when the result code is not zero.
FAQs
subprocess-tee
We found that subprocess-tee demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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.