snync Logo

snync

0
Free
Visit Website

When you manage private open source packages, for reasons such as keeping intellectual property private, then these packages will be hosted and served via private registries, or require authorization. By definition, these packages won't exist on public registries. However, when a package name is used without a reserved namespace (also known as a scope in npm, for example), they are often free to be registered by any other user on the Internet and create a potential Dependency Confusion attack vector. The attack manifests due to a mix of user misconfiguration, and bad design of package managers, which will cause the download of the package from the public registry, instead of the private registry. This tool detects two types of potential Dependency Confusion compromises: - Vulnerable - Suspicious Vulnerable: A case of actual vulnerable package is when a package name is detected to be used in a project, but the same package name is not registered on the public registry.

FEATURES

ALTERNATIVES

A browser with XSS detection capabilities

Integrates static APK analysis with Yara and requires re-compilation of Yara with the androguard module.

InQL is a Burp Suite extension for advanced GraphQL testing and vulnerability detection

Static security code scanner (SAST) for Node.js applications with Docker support and integrations with Slack.

Drltrace is a dynamic API calls tracer for Windows and Linux applications.

A web-based tool for instrumenting and analyzing Android applications using Flask, Jinja, and Redis.

Automatically redirect users from www to non-www for a secure connection.

A simple, secure framework for building scalable applications