System.Security.Cryptography.Encryptionv4.0.0-beta-22605

removed

Copy SHA256

License: unknown

Published:

Provides base types for symmetric and asymmetric cryptographic algorithms. Commonly Used Types: System.Security.Cryptography.ICryptoTransform System.Security.Cryptography.AsymmetricAlgorithm System.Security.Cryptography.SymmetricAlgorithm System.Security.Cryptography.KeySizes System.Security.Cryptography.CryptographicException System.Security.Cryptography.CipherMode System.Security.Cryptography.PaddingMode System.Security.Cryptography.CryptoStream System.Security.Cryptography.CryptoStreamMode

Fail

Incident: Removal

Caution: Package removed!

Incidents

Type: removalReported By: Community

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

No evidence of software tampering

Malware

No evidence of malware inclusion

Downloads

N/A

Total Downloads

Maintenance

Contributor

Dependencies

Declared Dependencies

Dependents

FAQ for System.Security.Cryptography.Encryption

What is System.Security.Cryptography.Encryption?

Is System.Security.Cryptography.Encryption malicious or is it safe to use?

The .NET package System.Security.Cryptography.Encryption has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. 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 System.Security.Cryptography.Encryption package were removed.

Is System.Security.Cryptography.Encryption popular?

The .NET package System.Security.Cryptography.Encryption is not widely used. 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 System.Security.Cryptography.Encryption once it is in my app?

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