Vulnerability Database · NuGet · Package report

OtpCsharp: vulnerability history, versions and safety

OtpCsharp is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in NuGet →

Vulert verdict on OtpCsharp i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for OtpCsharp is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Long-term outlook: risky 1 vulnerability on record across 1 year, none in the last year.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 25 Jun 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for OtpCsharp, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.1.1 C1 No Details →
2.1.0 C1 No Details →
1.0.200 C1 No Details →
1.0.199 C1 No Details →
1.0.198 C1 No Details →
1.0.197 C1 No Details →
1.0.196 C1 No Details →
1.0.195 C1 No Details →
1.0.194 C1 No Details →
1.0.193 C1 No Details →
1.0.192 C1 No Details →
1.0.191 C1 No Details →
1.0.190 C1 No Details →
1.0.189 C1 No Details →
1.0.188 C1 No Details →
1.0.187 C1 No Details →
1.0.186 C1 No Details →
1.0.185 C1 No Details →
1.0.184 C1 No Details →
1.0.183 C1 No Details →
1.0.182 C1 No Details →
1.0.181 C1 No Details →
1.0.180 C1 No Details →
1.0.179 C1 No Details →
1.0.178 C1 No Details →
1.0.177 C1 No Details →
1.0.176 C1 No Details →
1.0.175 C1 No Details →
1.0.174 C1 No Details →
1.0.173 C1 No Details →
1.0.172 C1 No Details →
1.0.171 C1 No Details →
1.0.170 C1 No Details →
1.0.169 C1 No Details →
1.0.168 C1 No Details →
1.0.167 C1 No Details →
1.0.166 C1 No Details →
1.0.165 C1 No Details →
1.0.164 C1 No Details →
1.0.163 C1 No Details →
1.0.162 C1 No Details →
1.0.161 C1 No Details →
1.0.160 C1 No Details →
1.0.159 C1 No Details →
1.0.158 C1 No Details →
1.0.157 C1 No Details →
1.0.156 C1 No Details →
1.0.155 C1 No Details →
1.0.154 C1 No Details →
1.0.153 C1 No Details →
1.0.152 C1 No Details →
1.0.151 C1 No Details →
1.0.150 C1 No Details →
1.0.149 C1 No Details →
1.0.148 C1 No Details →
1.0.147 C1 No Details →
1.0.146 C1 No Details →
1.0.145 C1 No Details →
1.0.144 C1 No Details →
1.0.143 C1 No Details →
1.0.142 C1 No Details →
1.0.141 C1 No Details →
1.0.140 C1 No Details →
1.0.139 C1 No Details →
1.0.138 C1 No Details →
1.0.137 C1 No Details →
1.0.136 C1 No Details →
1.0.135 C1 No Details →
1.0.134 C1 No Details →
1.0.133 C1 No Details →
1.0.132 C1 No Details →
1.0.131 C1 No Details →
1.0.130 C1 No Details →
1.0.129 C1 No Details →
1.0.128 C1 No Details →
1.0.127 C1 No Details →
1.0.126 C1 No Details →
1.0.125 C1 No Details →
1.0.124 C1 No Details →
1.0.123 C1 No Details →
1.0.122 C1 No Details →
1.0.121 C1 No Details →
1.0.120 C1 No Details →
1.0.119 C1 No Details →
1.0.118 C1 No Details →
1.0.117 C1 No Details →
1.0.116 C1 No Details →
1.0.115 C1 No Details →
1.0.114 C1 No Details →
1.0.113 C1 No Details →
1.0.112 C1 No Details →
1.0.111 C1 No Details →
1.0.110 C1 No Details →
1.0.109 C1 No Details →
1.0.108 C1 No Details →
1.0.107 C1 No Details →
1.0.106 C1 No Details →
1.0.105 C1 No Details →
1.0.104 C1 No Details →
1.0.103 C1 No Details →
1.0.102 C1 No Details →
1.0.101 C1 No Details →
1.0.100 C1 No Details →
1.0.99 C1 No Details →
1.0.98 C1 No Details →
1.0.97 C1 No Details →
1.0.96 C1 No Details →
1.0.95 C1 No Details →
1.0.94 C1 No Details →
1.0.93 C1 No Details →
1.0.92 C1 No Details →
1.0.91 C1 No Details →
1.0.90 C1 No Details →
1.0.89 C1 No Details →
1.0.88 C1 No Details →
1.0.87 C1 No Details →
1.0.86 C1 No Details →
1.0.85 C1 No Details →
1.0.84 C1 No Details →
1.0.83 C1 No Details →

Newest 120 of 202 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for OtpCsharp

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About OtpCsharp

Is OtpCsharp safe to use?

No. Vulert records a malicious-package vulnerability for OtpCsharp: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

How many vulnerabilities does OtpCsharp have?

1 vulnerability is recorded for OtpCsharp in the NuGet ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new OtpCsharp vulnerabilities disclosed?

0 vulnerabilities were recorded for OtpCsharp in the last 12 months, and the oldest entry in this database dates to 25 Jun 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of OtpCsharp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor OtpCsharp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the OtpCsharp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.