Spectra Assure
Community
  • Toolbox
  • Explore
  • Learn
  • ReversingLabs
    • Spectra Assure
    Community
    Quarantine
    Scanned: 18 days ago

    jwrincident

    Artifact:
    latest
    removed
    malicious
    Research
    A utility package
    License: unknown
    Published: 8 months 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
    2 malware-like behaviors found
    Malware
    5 supply chain attack artifacts

    INCIDENTS FOR THIS VERSION:

    malware
    8 months agoReported By: ReversingLabs (Researcher)
    Learn more about malware detection
    removal
    7 months agoReported By: Community
    malware
    6 months agoReported By: Community (kam193)
    More info
    malware
    6 months agoReported By: Community (OpenSSF)
    More info
    malware
    3 months agoReported By: Community (GitHub Advisory)
    More info
    Overviewissues10vulnerabilities0malware4behaviors9dependencies0contributors1versions2

    FAQ for jwrincident

    What is jwrincident?

    A utility package.

    Is jwrincident malicious or is it safe to use?

    The Python package jwrincident has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. 2 other issues and risky behaviors were found. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the jwrincident package were malicious.

    Is jwrincident popular?

    The Python package jwrincident is not widely used. It has 253 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 jwrincident once it is in my app?

    Since we can't know when or where malicious attacks will happen, we recommend tracking how jwrincident behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a jwrincident 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.