Kazama Senshi security record

As of 2 Nov 2026, Kazama Senshi has 2 audit reports by 1 security firm on Trustblock; the latest is by Cyberscope, dated 20 Sep 2022. Those reports list 1 open critical finding. It also holds 1 deployed contract on 1 chain.

Critical findings
1 open critical finding
Reported in “Kazama Senshi” by Cyberscope, Sep 2022. Not marked fixed in that report. See the findings
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.

Audits2

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Kazama SenshiSecurity firm: CyberscopeDate: Scope: 1 address on BNB Chain1 open critical findingOpen · cyberscope.io
Kazama SenshiSecurity firm: CyberscopeDate: Scope: 1 address on BNB Chain1 open critical findingOpen · IPFS

Findings7

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical100
High000
Medium000
Low600

No acknowledged finding in these reports.

Contracts1

AddressChainSource code
0x0fea9f83e029f54a46f8e8dd507bdd59ed1c57acChain: BNB ChainSource code: Verified source

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="kazama-senshi"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us