Spectra Assure
Community
failIncident: Malware
Scanned: about 22 hours ago

bittensor-burn-monitor

Artifact:
latest
removed
malicious
Research
Bittensor subnet burn rate monitoring
License: Permissive (MIT)
Published: about 2 months ago
See on PyPI

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 active web service credentials

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
4 low priority mitigations absent

Threats

Tampering
1 components prone to hijacking
Malware
1 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
about 2 months agoReported By: Community (kam193)
More info
malware
about 2 months agoReported By: Community (OpenSSF)
More info
removal
about 2 months agoReported By: Community
malware
about 22 hours agoReported By: ReversingLabs (Automated)
Learn more about malware detection
malware
N/AReported By: ReversingLabs (Researcher)
Learn more about malware detection
Overviewissues11vulnerabilities0malware2behaviors11dependencies1contributors1versions7

FAQ for bittensor-burn-monitor

What is bittensor-burn-monitor?

Bittensor subnet burn rate monitoring.

Is bittensor-burn-monitor malicious or is it safe to use?

The Python package bittensor-burn-monitor 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. 1 other issue and risky behavior was 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 bittensor-burn-monitor package were malicious.

Is bittensor-burn-monitor popular?

The Python package bittensor-burn-monitor is not widely used. It has 11K 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 bittensor-burn-monitor once it is in my app?

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

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.