arithmetic-bectoken.sol
VSS-20261003-OX80LH19 · generated Oct 3, 2026, 7:53 PM
Verdict is derived from severity counts via the same deterministic formula every VegaSec report uses. arithmetic-bectoken.sol was scanned from pasted source. This is static-analysis triage, not a certification or formal audit attestation.
PDF artifact
Queued artifact pipeline · not blocking on the scan
No PDF artifact has been requested for this report yet. The HTML report and the Markdown export already carry the full disclaimer and limitations inline. PDF synthesis is a queued artifact, not part of the scan path.
Status endpoint
GET /report/solidity/VSS-20261003-OX80LH19/export.pdf
Solidity evidence report
17 audit findings
Severity distribution
Executive summary
- 17 findings surfaced (0 critical, 1 high, 0 medium, 0 low, 16 informational).
- HIGH · Batch helper multiplies a count derived from a dynamic array by a caller-supplied amount and stores the product without a bounds check — exploitability medium.
- Automated static analysis only. A human operator review has not been attached to this report.
Warnings (1)
- · Unmapped detector slither:too-many-digits — classified as 'other'
- highMath / overflowConfidence: mediumExploitability: mediumDetector: semgrep
Batch helper multiplies a count derived from a dynamic array by a caller-supplied amount and stores the product without a bounds check
Evidence
Batch helper multiplies a count derived from a dynamic array by a caller-supplied amount and stores the product without a bounds check. On Solidity < 0.8 the multiply wraps silently (SWC-101 / batchOverflow class): a huge amount overflows to a small total, passes the balance check and credits every receiver. Use SafeMath/.mul, require the product to fit, or move to Solidity >= 0.8 checked arithmetic.
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Confirm the solc version uses checked arithmetic (>=0.8) or wrap mutations in OpenZeppelin SafeMath. Avoid unchecked blocks unless explicitly justified.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Version constraint ^0.4.16 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html)
Evidence
Version constraint ^0.4.16 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html) - DirtyBytesArrayToStorage - ABIDecodeTwoDimensionalArrayMemory - KeccakCaching - EmptyByteArrayCopy - DynamicArrayCleanup - ImplicitConstructorCallvalueCheck - TupleAssignmentMultiStackSlotComponents - MemoryArrayCreationOverflow - privateCanBeOverridden - SignedArrayStorageCopy - ABIEncoderV2StorageArrayWithMultiSlotElement - DynamicConstructorArgumentsClippedABIV2 - UninitializedFunctionPointerInConstructor_0.4.x - IncorrectEventSignatureInLibraries_0.4.x - ExpExponentCleanup - NestedArrayFunctionCallDecoder - ZeroFunctionSelector. It is used by: - ^0.4.16 (arithmetic-bectoken.sol#7)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter BasicToken.transfer(address,uint256)._value (arithmetic-bectoken.sol#65) is not in mixedCase
Evidence
Parameter BasicToken.transfer(address,uint256)._value (arithmetic-bectoken.sol#65) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter BasicToken.balanceOf(address)._owner (arithmetic-bectoken.sol#81) is not in mixedCase
Evidence
Parameter BasicToken.balanceOf(address)._owner (arithmetic-bectoken.sol#81) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter StandardToken.transferFrom(address,address,uint256)._from (arithmetic-bectoken.sol#116) is not in mixedCase
Evidence
Parameter StandardToken.transferFrom(address,address,uint256)._from (arithmetic-bectoken.sol#116) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter StandardToken.approve(address,uint256)._value (arithmetic-bectoken.sol#138) is not in mixedCase
Evidence
Parameter StandardToken.approve(address,uint256)._value (arithmetic-bectoken.sol#138) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter StandardToken.allowance(address,address)._spender (arithmetic-bectoken.sol#150) is not in mixedCase
Evidence
Parameter StandardToken.allowance(address,address)._spender (arithmetic-bectoken.sol#150) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter PausableToken.transfer(address,uint256)._value (arithmetic-bectoken.sol#249) is not in mixedCase
Evidence
Parameter PausableToken.transfer(address,uint256)._value (arithmetic-bectoken.sol#249) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter PausableToken.transferFrom(address,address,uint256)._from (arithmetic-bectoken.sol#253) is not in mixedCase
Evidence
Parameter PausableToken.transferFrom(address,address,uint256)._from (arithmetic-bectoken.sol#253) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter PausableToken.approve(address,uint256)._spender (arithmetic-bectoken.sol#257) is not in mixedCase
Evidence
Parameter PausableToken.approve(address,uint256)._spender (arithmetic-bectoken.sol#257) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
batchTransfer(address[],uint256) should be declared external:
Evidence
batchTransfer(address[],uint256) should be declared external: - PausableToken.batchTransfer(address[],uint256) (arithmetic-bectoken.sol#261-274)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Parameter PausableToken.batchTransfer(address[],uint256)._receivers (arithmetic-bectoken.sol#261) is not in mixedCase
Evidence
Parameter PausableToken.batchTransfer(address[],uint256)._receivers (arithmetic-bectoken.sol#261) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
BecToken.name (arithmetic-bectoken.sol#289) should be constant
Evidence
BecToken.name (arithmetic-bectoken.sol#289) should be constant
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
BecToken.symbol (arithmetic-bectoken.sol#290) should be constant
Evidence
BecToken.symbol (arithmetic-bectoken.sol#290) should be constant
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
BecToken.version (arithmetic-bectoken.sol#291) should be constant
Evidence
BecToken.version (arithmetic-bectoken.sol#291) should be constant
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
BecToken.decimals (arithmetic-bectoken.sol#292) should be constant
Evidence
BecToken.decimals (arithmetic-bectoken.sol#292) should be constant
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
BecToken.BecToken() (arithmetic-bectoken.sol#297-300) uses literals with too many digits:
Evidence
BecToken.BecToken() (arithmetic-bectoken.sol#297-300) uses literals with too many digits: - totalSupply = 7000000000 * (10 ** (uint256(decimals))) (arithmetic-bectoken.sol#298)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
Exploit reasoning
Reference-grade reasoning tied to evidence
- d7260e05a127d4f97d5b54826e692574c382409b9e94474b8ed37a9645630369 · math-overflowhighConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Arithmetic outside Solidity 0.8+ overflow checks (assembly, unchecked block, or compiler < 0.8)
- Caller-controlled inputs reach the arithmetic without bounds checks
Action
Attacker passes inputs that wrap a balance or counter past its boundary, producing values that pass downstream checks.
Impact
Inflated balances, bypass of cap checks, or denial-of-service when iteration counters wrap.
False-positive caveats
- Unchecked blocks are sometimes intentional (gas optimization on values bounded by other invariants).
- Compiler ≥ 0.8.0 reverts on overflow unless the code explicitly opts out.
Remediation checklist
- Move arithmetic out of the unchecked block.
- Bound caller inputs with explicit require() before arithmetic.
- Upgrade compiler to ≥ 0.8.0 when feasible and remove SafeMath wrappers.
Audit pipeline
Audit cockpit
Honest stage-by-stage view of what VegaSec ran against this contract. Automated stages do not replace a human operator review.
Audit intake
Passed320ms replay7:53 PMNormalize the submitted contract target and confirm it can enter the Solidity audit lane.
Source acquisition
Passed1.4s replay7:53 PMResolve pasted source or verified explorer source without treating malformed input as demo data.
Toolchain validation
Partial2.3s replay7:53 PMConfirm the configured static analyzers can run and produce parseable output.
- One or more analyzers emitted warnings; report findings remain usable but should be read with limitations.
Static analysis
Partial17 findings8.8s replay7:53 PMRun static analyzers against the sandboxed source and collect raw detector evidence.
- One or more analyzers emitted warnings; report findings remain usable but should be read with limitations.
Finding normalization
Passed17 findings1.1s replay7:53 PMDedupe detectors, classify vulnerability classes and compute severity-weighted risk.
Exploitability review
Partial17 findings1.9s replay7:53 PMFrame automated findings with conservative exploitability and limitation notes.
- Automated exploitability review is conservative and does not replace a manual exploitability assessment.
Remediation draft
Partial17 findings1.5s replay7:53 PMPrepare remediation-oriented evidence for the shareable report artifact.
- Remediation notes are generated from detector evidence and require project-specific engineering review.
Operator review
Blocked0ms replay7:53 PMRecord whether a human operator artifact exists before buyer escalation.
- No operator review artifact is attached to this automated scan.
- Human operator review has not been attached to this automated scan yet.
Finalization
Partial17 findings620ms replay7:53 PMPublish the automated report artifact or explain why the scan failed closed.
Artifact: Automated Solidity report · solidity-2f746d702f766567
- Final report is an automated static-analysis artifact; no operator review artifact is attached.
How to read this report
Score, confidence, ranking: four moving parts, no hand-tuning.
Generated Oct 3, 2026, 7:53 PM · Solidity · arithmetic-bectoken.sol
Score bands
0-19
AVOID-style triage
Multiple high or critical findings, low source confidence, or unverified context. Public action should pause until a Private Review or a re-scan with better evidence.
20-49
High caution
Notable findings or thin evidence. Worth a Private Review before relying on the artifact.
50-69
Watch
Mixed signals: some evidence, some gaps. Re-scan after material changes to the target.
70-89
Clear surface (automated)
No critical or high findings via static analysis. Not a safety claim: human review is still recommended for diligence work.
90-100
Strong surface (automated) · this report
No critical or high findings, verified source, and high source confidence. Not a safety claim: human review is still recommended for diligence work.
- Score
- Deterministic 0-100 derived from severity counts. Same formula across every report. Lower means more risk.
- Confidence
- Separate axis. Measures how much VegaSec trusts the input data. Low confidence pushes the verdict toward UNKNOWN; the two are never collapsed into one number.
- Ranking / percentile
- Only meaningful within the eligible Trust Index set. Shown on /trust-index when the eligible pool is large enough. Today the public index is a controlled preview.
Private Review is separate
A paid Private Review does not raise the public score on this report. Public score reflects public-source evidence only. Private Review adds operator attestation and a confidential memo, never a score bump.