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 is a Python library that enables you to use video cameras from Python on Windows. It is based on DirectShow. In particular, it allows to:
The library is available on PyPI: https://pypi.org/project/pygrabber/0.1/
# This code lists the cameras connected to your PC:
from pygrabber.dshow_graph import FilterGraph
graph = FilterGraph()
print(graph.get_input_devices())
# Captures a frame from the first camera found on your computer every second and saves it to a file
import cv2
from datetime import datetime
from threading import Event, Thread
from pygrabber.dshow_graph import FilterGraph
from os import path
PAUSE_BETWEEN_CAPTURE = 1 # 1 sec.
OUTPUT_FOLDER = r"C:\test\\"
CAMERA_INDEX = 0 # Using first camera found
global start_time
def capture_photos_loop(event_):
global start_time
start_time = datetime.now()
while not event_.isSet():
graph.grab_frame()
event_.wait(PAUSE_BETWEEN_CAPTURE)
def show_image(image):
global start_time
capture_time = datetime.now() - start_time
image_file_name = path.join(OUTPUT_FOLDER, str(capture_time.seconds * 1000 + int(capture_time.microseconds / 1000)) + ".jpg")
cv2.imwrite(image_file_name, image)
print(f"Image {image_file_name} written")
if __name__ == "__main__":
event = Event()
capture_thread = Thread(target=capture_photos_loop, args=(event, ))
graph = FilterGraph()
devices = graph.get_input_devices()
print(f"Connecting to device {devices[CAMERA_INDEX]}")
graph.add_video_input_device(CAMERA_INDEX)
graph.add_sample_grabber(lambda image: show_image(image))
graph.add_null_render()
graph.prepare_preview_graph()
graph.run()
capture_thread.start()
input(f"Capturing images every {PAUSE_BETWEEN_CAPTURE}s, press ENTER to terminate.")
event.set()
capture_thread.join()
print("Done")
# This code shows a screen with the live image from the first camera in your PC.
# We add to the graph two filters: one is a source filter corresponding to the first camera connected to your PC,
# the second is the default render, that shows the images from the camera in a window on the screen.
# Then we call prepare, that connects the two filters together, and run, to execute the graph.
# Finally, we need a method to pause the program while watching the camera video.
# I use the Tkinter mainloop function which fetches and handles Windows events, so the application does't seem frozen.
from pygrabber.dshow_graph import FilterGraph
from tkinter import Tk
graph = FilterGraph()
graph.add_video_input_device(0)
graph.add_default_render()
graph.prepare_preview_graph()
graph.run()
root = Tk()
root.withdraw() # hide Tkinter main window
root.mainloop()
See also the other examples on the "examples" folder and the article https://www.codeproject.com/Articles/1274094/%2FArticles%2F1274094%2FCapturing-images-from-camera-using-Python-and-Dire.
The file run_gui.py will run a tool with a GUI that enables you to use a camera connected to your system, capture still frames or videos, do basic image porcessing.
FAQs
Module for grabbing live video images using DirectShow
We found that pygrabber 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.