The 'log' crate (official Rust logging facade) contains a hardcoded IPv6 literal only inside std::net value-conversion / test code for the kv module. No network calls, exfiltration, or C2 behavior exists; the finding is a false-positive heuristic match on an example/test address.
AI breakdown
Plain-English summary of what this package does and how it behaves.
The 'log' package (v0.4.34) is the standard Rust logging facade crate. It provides traits, macros, and utilities for emitting log records with optional key-value data.
Capabilities
- Provides logging macros and traits
- Supports key-value structured logging
- No scripts or dependencies declared
Data access
- None observed
Network
- Hardcoded public IP in network code (static findings)
Standard logging library with no observed runtime side effects; static analysis flagged potential hardcoded IPs that should be reviewed in context of the crate's source.
Security findings (2)
Static analysis rule matches, with the exact code that triggered them.
File src/kv/value.rs contains a hardcoded public IP (f33c::1) used in network code — review for hidden exfiltration or C2 endpoints.
File log-0.4.34/src/kv/value.rs contains a hardcoded public IP (f33c::1) used in network code — review for hidden exfiltration or C2 endpoints.
Files in package (46)
How ShadowCanopy checks crates.io packages
ShadowCanopy blocks every dependency by default and only lets through what it can verify — against live malicious-package advisories, an AI behavior scan, and a byte-for-byte hash check. It protects installs across npm, PyPI, crates.io, pkg.go.dev, RubyGems, Maven Central, NuGet, Packagist, Hex, pub.dev, Swift Package Manager.
This report reflects ShadowCanopy's threat intelligence at page load and is informational, not a warranty. Canonical URL: https://shadowcanopy.dev/packages/crates/log