Honeypot, rug-pull and ownership checks

Is KiboShib a Scam?

KIBSHI

Ethereum

Not verified

This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →

Last checked Sep 4, 2026 · 1 audit on record

Chart

0/ 100

Low RiskHow is this score calculated?

How the score breaks downratings: 10 is safest

Technical10/10 Governance6/10 Upgrades7/10 Checks passed6 of 7 Findings1 Low · 2 Info3

SummaryAI Copilot

The KiboShib contract implements a standard ERC20 token. The code is well-structured and largely adheres to common ERC20 patterns, including safe arithmetic for subtractions.

Read the full analysis

What raised the score

Ownership status UNKNOWN
1 Low finding(s) from audit

Exact factors

Ownership status UNKNOWN (owner could not be resolved)
1 Low finding(s) from audit

Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed

Our automated scanner reviewed KiboShib (KIBSHI) on Ethereum. 6 of 7 security checks passed — see the full breakdown below.

Security Checklist

as of audit · Sep 46 of 7 checks passed

Contract verifiedVerified

OwnershipUnknown

MintNo mint

Liquidity lockLocked

UpgradeabilityFixed code

HoneypotNone found

Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026

ContractsWalletsEveryone elseBubble area = share of supply

22.3%of supply sits with the top 10 holders

Contractstreasury, vesting, bridge, staking12.8%
Walletsanonymous holders, free to sell9.5%
Everyone elsethe rest of the supply77.7%

Effective concentrationwhat the score reads14.6%

How holder types affect the score

Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.

Holder balances as recorded by the audit of Sep 4, 2026

Liquidity

as of audit · Sep 4$368.4K across 5 pairs

The risk score reads depth across every pair.

LP tokensLocked

The LP tokens of the analysed pool are locked or burned.

Analysed pool$360.3KShare of depth97.8%

LP Locked100.0% · DxLock, Null Address

Unlocked LP held by

0x1f2f…f387

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

Security Findings

1 Low2 Info

Low

Lack of Emergency Pausability

The contract does not include a mechanism to pause token transfers in emergency situations. This could prevent mitigation of issues like critical vulnerabilities or unexpected market events, potentially leading to irreversible losses or exploits if a rapid response is required. While not a direct vulnerability, it limits the project's ability to react to crises.L-01

Issue

Fix

Consider implementing a pausable mechanism, typically controlled by a multi-signature wallet or a trusted governance entity. This would allow for temporary suspension of critical operations in case of an emergency, providing a window to address severe issues.

Status

Unresolved

Info

Custom ERC20 Implementation

The project utilizes a custom implementation of the ERC20 standard rather than leveraging battle-tested and widely audited libraries like OpenZeppelin. While the provided code appears to adhere to the standard, custom implementations carry a higher inherent risk of subtle bugs or non-standard behaviors compared to established libraries that have undergone extensive community review and formal audits.I-01

Issue

Fix

For future projects, it is generally recommended to use well-vetted and audited libraries such as OpenZeppelin Contracts for standard functionalities. If a custom implementation is necessary, ensure it undergoes thorough testing and independent security audits.

Status

Unresolved

Info

Centralized Initial Token Distribution

The entire initial supply of 1,000,000,000,000 * 10^18 tokens is minted to the contract deployer's address. This grants the deployer significant control over the token's supply, liquidity, and potential market dynamics, posing a centralization risk. While common for new tokens, it concentrates power in a single entity.I-02

Issue

Fix

Ensure that the deployer's address is secured with robust measures, such as a hardware wallet or a multi-signature wallet. For long-term decentralization, consider mechanisms for distributing token control or vesting schedules for large token allocations.

Status

Unresolved

Analysis

AI Copilotas of audit · Sep 4

Executive SummaryWhat the contract is and what the review found

The KiboShib contract implements a standard ERC20 token. The code is well-structured and largely adheres to common ERC20 patterns, including safe arithmetic for subtractions. Key areas of review included adherence to ERC20 standards, access control, and potential economic implications. The audit identified a low-severity issue regarding the lack of an emergency pause mechanism and informational findings related to the custom ERC20 implementation and centralized initial token distribution.

Technical10/10Low risk

The contract implements the ERC20 standard, providing basic token functionalities such as transfer, approval, and balance management (7.1 Architecture). Code security is generally good, with appropriate use of require statements and unchecked blocks for arithmetic operations where bounds are checked (7.2 Code Security). Access control (7.3 Access Control) is standard for an ERC20 token, with no additional privileged roles beyond the deployer receiving the initial supply. A minor concern is the absence of an emergency pause function, which could limit response capabilities during unforeseen events.

Governance6/10Medium risk

The economic model (7.4 Economic) involves a large initial supply minted entirely to the deployer, which centralizes control over the token's initial distribution and market dynamics. There are no explicit governance mechanisms (7.5 Governance) within the contract itself, as it functions as a simple token. External factors, such as liquidity provision and market behavior, will significantly influence the token's economic stability.

Upgrades7/10Low risk

The KiboShib contract is not designed to be upgradeable (7.7 Upgrades). It is deployed as a standard, immutable contract, which eliminates risks associated with upgrade mechanisms but also prevents future modifications or bug fixes to the contract logic.

Final RecommendationWhat to do about this score

It is recommended to consider implementing an emergency pause mechanism to provide a safety net against unforeseen vulnerabilities or market disruptions.

While the current ERC20 implementation is robust, for future projects, leveraging battle-tested libraries like OpenZeppelin is advised to benefit from extensive community audits and ongoing security improvements. Ensure that the deployer's private key is secured with the highest standards, given the significant control over the initial token supply.

Contract & Record

1 audit on record

TypeToken

NetworkEthereum

Token age3y

Contract0x02e7…2361

Deployer0x1dc6…6c42

Badge for your website

Free for any token on the record. It links to this page and always shows the current score and the date it was checked.

Audit History

Sep 4, 20260Low

Score changes are recorded as dated snapshots — history is append-only and cannot be edited.

Frequently Asked Questions

What is the KIBSHI contract address?

The KiboShib (KIBSHI) contract on Ethereum is 0x02e7f808990638e9e67e1f00313037ede2362361. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.