Check your dependencies for malware and vulnerabilities without leaving VS Code

Meet Spectra Code, for free

Get the extension
Spectra Assure
Community
  • Toolbox
  • Explore
  • Learn
  • ReversingLabs
    • Spectra Assure
    Community
    Quarantine
    Scanned: 9 days ago

    password-cracker-DO-NOT-USE

    0.0.1
    Artifact:
    password_cracker_DO_NOT_USE-0.0.1-py3-none-any.whl
    latest
    malicious
    this package is for testing purposes
    License: Permissive (MIT)
    Published: about 4 years ago
    See on PyPI

    SAFE Assessment

    Compliance

    Licenses
    No license compliance issues
    Secrets
    No sensitive information found

    Security

    Vulnerabilities
    No known vulnerabilities detected
    Hardening
    No application hardening issues

    Threats

    Tampering
    1 quarantined components found
    Malware
    1 malicious components found

    INCIDENTS FOR THIS VERSION:

    malware
    over 1 year agoReported By: ReversingLabs (Automated)
    Learn more about malware detection
    Overviewissues7vulnerabilities0malware1behaviors25dependencies0contributors0versions1

    FAQ for password-cracker-DO-NOT-USE

    What is password-cracker-DO-NOT-USE?

    this package is for testing purposes.

    Is password-cracker-DO-NOT-USE malicious or is it safe to use?

    The Python package password-cracker-DO-NOT-USE was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 1 other issue and risky behavior was found. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the password-cracker-DO-NOT-USE package were malicious.

    Is password-cracker-DO-NOT-USE popular?

    The Python package password-cracker-DO-NOT-USE is not widely used. It has 4K recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

    How do I secure password-cracker-DO-NOT-USE once it is in my app?

    Since we can't know when or where malicious attacks will happen, we recommend tracking how password-cracker-DO-NOT-USE behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a password-cracker-DO-NOT-USE version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

    Did you know...

    ... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

    We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.