오프라인 상태 — 캐시된 데이터 표시 중
BibaMoney TVIJO AIOS NETWORK
GOGA 데모 사용해보기
BTC $63445.00 ▼-2.80% ETH $1874.90 ▼-4.50% USDT $1.00 ▲+0.00% BNB $566.53 ▼-1.20% USDC $1.00 ▲+0.00% XRP $1.05 ▼-5.10% SOL $73.17 ▼-4.40% TRX $0.33 ▼-1.60% FIGR_HELOC $1.03 ▲+0.20% WBT $55.43 ▼-3.20% HYPE $54.49 ▼-9.80% DOGE $0.07 ▼-3.80%

Live security feed + exchange risk lab

Security Alerts & Exchange Risk Lab

Tvijo AIOS relays security advisories and turns them into practical risk signals for crypto users: scams, exchange failures, copytrading drift, bot drawdowns, and high-leverage liquidation traps.

MEXC Gate.io Bybit OKX Copytrading x100 / x200 / x500

5분마다 자동 새로고침. 아직 블록체인 RPC 호출은 없으며, 온체인 이상 징후는 플레이스홀더입니다.

Wondering how the platform itself is secured? Read our Platform Security statement.

알림
60
Critical
13
높음
47
소스
2
영향을 받는 스타트업
0

Exchange Risk Radar

User protection layer

Why deposits disappear

Most losses are not hacks. They are missing limits.

This risk lens follows the failure modes users actually meet on exchanges: copied traders changing risk, bots averaging into liquidation, API keys with too much power, and leverage bands where a tiny move can erase margin.

View loss scenarios Live alerts
Bybit Copytrading drift Follower entry price, margin mode, and master-trader hedge can diverge.
OKX Bot guardrails Grid/DCA bots need hard daily loss caps, position caps, and kill switches.
Gate.io Listing and liquidity risk Thin books, delistings, and transfer network mistakes can trap capital.
MEXC Extreme leverage Very high leverage turns normal volatility, fees, and slippage into liquidation.

Deposit Loss Map

Educational risk model, separate from the live alert counters below.
카피트레이딩

Follower risk is not master risk

Users can enter later, receive different fills, copy a larger effective position, or miss the master trader's hedge. A profitable leader can still liquidate followers.

  • Show copied leverage before follow.
  • Block martingale-style size jumps.
  • Stop copying when drawdown exceeds the user's cap.
Exchange bots

Automation without a hard stop drains slowly, then suddenly

Grid, DCA, and signal bots can keep adding exposure after the thesis breaks. Without loss limits, one bad regime can consume the full deposit.

  • No withdrawal permission on API keys.
  • Daily loss, max orders, and max notional ceilings.
  • Emergency pause after repeated failed exits.
High leverage

x100 / x200 / x500 is a liquidation product

At extreme leverage, ordinary candle noise, funding, spread, and liquidation fees can erase margin before a human has time to react.

  • Default to low leverage; require friction above the cap.
  • Separate isolated margin from cross-collateral.
  • Show liquidation distance in price, not only percent.
Operational risk

The loss can start outside the trade

Wrong deposit networks, fake support links, compromised sessions, stale API keys, delistings, or disabled withdrawals can convert a normal action into a capital lock.

  • Warn before network and memo mismatches.
  • Score exchange incidents and withdrawal friction.
  • Surface phishing and support impersonation alerts.

Guardrails the Lab Should Enforce

AIOS / GOGA roadmap
Risk budget first Position size, max daily loss, max open orders, and exchange exposure are set before any bot or copy strategy can run.
API permissions audit Trade-only keys are isolated per exchange. Withdrawal rights, stale keys, and broad account scopes are treated as critical risk.
Leverage ceiling Strategies are blocked or downgraded when leverage, liquidation distance, or cross-margin exposure breaks the user's safety profile.
Copytrader drift check Follower fills, master leverage, drawdown, symbol changes, and hidden averaging are monitored as live risk, not marketing performance.

AIOS / GOGA / Admin Connection

How public warnings connect to the product stack.
Public /security Live advisories, token checks, wallet screening, exchange risk education, and user-facing warnings.
GOGA 랩 Strategy safety scoring, bot drawdown simulation, copytrading anomaly review, and liquidation-distance analysis.
Admin App Collector health, cron status, provider failures, source freshness, risk taxonomy, and release readiness.

Filter the feed

Feed updated 1h ago
전체 critical · 13 high · 47 scam · 1 vulnerability · 56 breach · 3

Sources in this snapshot: hn (46), github_security (14). Counts are computed from the live normalized feed only — nothing is hand-curated.

활성 알림

심각 vulnerability github_security 3d ago

Shescape: Shell injection via unescaped parentheses on Windows with CMD

### Impact This impacts users of Shescape on Windows that explicitly configure `shell` to CMD, or `true` with the default shell being CMD, using the `escape` and `escapeAll` APIs. An attacker may be able to achieve shell injection depending on the original command. ```javascript import * as cp from "node:child_process"; import { Shescape } from "shescape"; // 1. Prerequisites const options = { shell: "cmd.exe", // Or shell: true, // Only if the default shell is CMD }; // 2. Payload const payload = "x) else if a==a (echo y"; // 3. Usage const shescape = new Shescape(options); let escapedPayload; escapedPayload = shescape.escape(payload); // Or escapedPayload = shescape.escapeAll([payload]); // And (example) const result = cp.execSync(`if defined FALSY (echo ${escapedPayload})`, options); // 4. Impact console.log(result.toString()); // Outputs "y" instead of "" ``` ### Patches This bug has been patched in [v2.1.14] and [v3.0.1] which you can upgrade to now. If yo

심각 vulnerability github_security 3d ago

sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock

## Summary `sm-crypto` (npm package **0.4.0**, the latest release, published 2026-01-20) generates SM2 private keys and signing ephemeral scalars from a single module-wide RNG instance (`src/sm2/utils.js`: `const rng = new SecureRandom()`). `SecureRandom` is jsbn's PRNG, which seeds an **ARC4** stream from `window.crypto.getRandomValues` when available. **In Node.js — sm-crypto's primary runtime — `window` is `undefined`, so the CSPRNG branch is skipped** and the seed pool is instead filled from `Math.random()` (V8 `xorshift128+`, recoverable from a few outputs) plus `new Date().getTime()` (wall clock, attacker-estimable). Node *does* expose Web Crypto as `globalThis.crypto`, but jsbn checks `window.crypto`, not `globalThis.crypto`, so the secure path is never taken. Consequently every SM2 private key produced by the default `sm2.generateKeyPairHex()` and every signing ephemeral scalar is derived from non-cryptographic sources and is **predictable** by an attacker who can observe a f

사기 경고

토큰 보안 확인

GoPlus 토큰 위험 스냅샷: 허니팟, 프록시, 발행 권한, 소유권 변경 등 계약 수준 검사.

토큰 계약 주소를 붙여넣어 최신 정규화된 위험 스냅샷을 확인하세요.

제재 확인

OpenSanctions 지갑 제재 데이터베이스 스크리닝. 이는 공개 읽기 전용 중계이며, 규정 준수 결정 엔진이 아닙니다.

지갑 주소를 붙여넣어 캐시된/실시간 스크리닝 중계를 실행하세요.

최근 취약점

심각 vulnerability github_security 3d ago

Shescape: Shell injection via unescaped parentheses on Windows with CMD

### Impact This impacts users of Shescape on Windows that explicitly configure `shell` to CMD, or `true` with the default shell being CMD, using the `escape` and `escapeAll` APIs. An attacker may be able to achieve shell injection depending on the original command. ```javascript import * as cp from "node:child_process"; import { Shescape } from "shescape"; // 1. Prerequisites const options = { shell: "cmd.exe", // Or shell: true, // Only if the default shell is CMD }; // 2. Payload const payload = "x) else if a==a (echo y"; // 3. Usage const shescape = new Shescape(options); let escapedPayload; escapedPayload = shescape.escape(payload); // Or escapedPayload = shescape.escapeAll([payload]); // And (example) const result = cp.execSync(`if defined FALSY (echo ${escapedPayload})`, options); // 4. Impact console.log(result.toString()); // Outputs "y" instead of "" ``` ### Patches This bug has been patched in [v2.1.14] and [v3.0.1] which you can upgrade to now. If yo

심각 vulnerability github_security 3d ago

sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock

## Summary `sm-crypto` (npm package **0.4.0**, the latest release, published 2026-01-20) generates SM2 private keys and signing ephemeral scalars from a single module-wide RNG instance (`src/sm2/utils.js`: `const rng = new SecureRandom()`). `SecureRandom` is jsbn's PRNG, which seeds an **ARC4** stream from `window.crypto.getRandomValues` when available. **In Node.js — sm-crypto's primary runtime — `window` is `undefined`, so the CSPRNG branch is skipped** and the seed pool is instead filled from `Math.random()` (V8 `xorshift128+`, recoverable from a few outputs) plus `new Date().getTime()` (wall clock, attacker-estimable). Node *does* expose Web Crypto as `globalThis.crypto`, but jsbn checks `window.crypto`, not `globalThis.crypto`, so the secure path is never taken. Consequently every SM2 private key produced by the default `sm2.generateKeyPairHex()` and every signing ephemeral scalar is derived from non-cryptographic sources and is **predictable** by an attacker who can observe a f

심각 vulnerability github_security 3d ago

kin-openapi: ValidationHandler.Load() Fail-Open Authentication Bypass via NoopAuthenticationFunc Default

### Summary `ValidationHandler.Load()` in `getkin/kin-openapi` silently replaces a nil `AuthenticationFunc` with `NoopAuthenticationFunc`, which always returns `nil` without performing any credential check. Because this substitution happens unconditionally when the caller omits the field, every OpenAPI `security` requirement declared in the spec is silently satisfied for unauthenticated requests. An unauthenticated remote attacker can reach handlers for routes whose OpenAPI operation requires an API key, OAuth token, or any other security scheme if the application relies on `ValidationHandler` as its enforcement middleware. ### Details `ValidationHandler` is an HTTP middleware exported by `openapi3filter` that validates incoming requests and responses against a loaded OpenAPI specification. Its `Load()` method initialises default fields before the handler begins serving: ```go // openapi3filter/validation_handler.go:47-49 if h.AuthenticationFunc == nil { h.AuthenticationFunc = N

HN 보안 다이제스트

How This Platform Is Secured

This page tracks external market threats. For how BibaMoney / Tvijo AIOS itself is protected, read the full statement:

  • Non-custodial: no funds held, no withdrawal access, ever.
  • Exchange keys sealed with AES-256-GCM; fail-closed vault, never shown or logged.
  • Read-only public surface: no write path from public pages to the database.
  • Strict CSP (no inline scripts), clickjacking and MIME-sniffing protection.
Platform Security statement

최근 사기 신고

Chainabuse/abuse-report 정규화가 아직 이 공개 인터페이스에 연결되지 않았습니다. 수집기가 도입되면 이 섹션에 새로 플래그된 지갑과 캠페인 노트가 표시됩니다.