peckshield Profile Banner
PeckShield Inc. Profile
PeckShield Inc.

@peckshield

Followers
82K
Following
3K
Media
471
Statuses
2K

A blockchain security and data analytics company (telegram: https://t.co/x72dANZur3)

Joined January 2018
Don't wanna be here? Send us removal request.
@peckshield
PeckShield Inc.
3 years
1/ We are thrilled to announce a self-service SaaS platform-#KillSwitch, which aims to detect exploitation TXs before their block inclusion and take contingency measures to block the attack or prevent assets from being stolen. It is in-essence a frontrunning-based DeFi protection
138
424
1K
@peckshield
PeckShield Inc.
19 days
It seems @Port3Network token contract w/ cross-bridge support on BSC has been compromised, resulting in an unauthorized mint of one billion (1_000_000_000) tokens. The minted tokens are immediately dumped and the price is tanked. Here is the unauthorized mint:
5
10
69
@premium
Premium
4 months
Why guess when you can know?
0
682
8K
@peckshield
PeckShield Inc.
1 month
fallout from oct 10 liquidity cringe?
@PeckShieldAlert
PeckShieldAlert
1 month
100% utilization on several curated vaults?! Wild. Shall we be concerned? 🔥 details: https://t.co/sDMGL0pEiG
8
6
37
@peckshield
PeckShield Inc.
1 month
Hi @Balancer, you may want to take a look:
67
38
427
@peckshield
PeckShield Inc.
3 months
🚨🚨🚨 For the time being, do *NOT* use any $SFUND bridges. A drain bridge hack just happened on one of $SFUND bridges
@meta_alchemist
Meta Alchemist
3 months
UPDATE: For the time being please do not use any $SFUND bridges.
6
11
44
@peckshield
PeckShield Inc.
3 months
🚨🚨🚨 Do *NOT* interact with $UXLINK token !!! The token is now compromised as today's @UXLINKofficial hacker has gained the mint role and 1B $UXLINK tokens were just minted on arbitrum. Here is the unauthorized 1B mint: https://t.co/JEiJ5HS8iR
@UXLINKofficial
UXLINK
3 months
Security Notice Update 2 We have identified an unauthorized minting of UXLINK tokens today by a malicious actor. The transaction can be viewed here: https://t.co/hpUjS3G8G0 This issuance is invalid as it violates the project’s official whitepaper. We strongly advise all
6
15
71
@peckshield
PeckShield Inc.
3 months
Also related to @Shibtoken
5
2
12
@GOLDCOUNCIL
World Gold Council
3 months
Elton John’s life has been touched by gold in fascinating ways, both on and off the stage. Hear his story, in a new exclusive access documentary. Elton John - Touched By Gold, out now.
0
1K
11K
@peckshield
PeckShield Inc.
3 months
Hi @ShytoshiKusama, you may want to take a look: https://t.co/mJPx86XUUc
54
28
162
@peckshield
PeckShield Inc.
3 months
@justinsuntron
H.E. Justin Sun 👨‍🚀 🌞
3 months
我们的地址只是笼统地做了几笔交易所充值测试,金额非常低,然后做了一个地址分散,没有涉及任何买卖,不可能对市场产生任何影响。
2
0
5
@peckshield
PeckShield Inc.
3 months
👀👀👀 A @justinsuntron-associated address (labeld as TRON DAO) was blacklisted after allegedly selling $WLFI Here is the related tx: https://t.co/HSd3WSSTmN
11
8
48
@VenusProtocol
Venus Protocol
3 months
It was amazing that we could to turn the tide and have the best possible outcome for all. Huge shout out to @peckshield @hexagate_ @HypernativeLabs @chaos_labs and the amazing Venus Community. This would not have worked out if one piece wasn't in place. Stay safe, everyone 💪
@KuanSun1990
Kuan Sun
3 months
Hey gus, I am the victim of the recent phishing attack on Venus. What could have been a total disaster turned into a battle we actually won — thanks to an incredible group of teams. 🙏 Here’s my gratitude thread 🧵
11
21
86
@VenusProtocol
Venus Protocol
3 months
39
47
157
@peckshield
PeckShield Inc.
3 months
Kudos to @VenusProtocol! The lost funds have now been recovered by force-liquidating the exploiter's position. Here is the related tx: https://t.co/5ibe0fldyv
@VenusProtocol
Venus Protocol
3 months
Update: Venus Protocol has been fully restored (withdrawals and liquidations resumed) as of 9:58PM UTC. ✅ The lost funds have been recovered under Venus' protection. ✅
10
23
145
@peckshield
PeckShield Inc.
3 months
Today, a user suffered a devastating phishing attack, and @VenusProtocol has responded swiftly and responsibly by proposing an Emergency Vote — a commendable step to ensure Venus resumes safely while working to recover the user’s stolen funds. Here is the vote details:
@PeckShieldAlert
PeckShieldAlert
3 months
#PeckShieldAlert A user of @VenusProtocol has been drained ~$27M in crypto after falling for a #phishing scam. The victim approved a malicious transaction, granting token approval to the attacker's address (0x7fd8...202a) for asset transfer.
4
5
45
@PeckShieldAlert
PeckShieldAlert
3 months
#PeckShieldAlert A user of @VenusProtocol has been drained ~$27M in crypto after falling for a #phishing scam. The victim approved a malicious transaction, granting token approval to the attacker's address (0x7fd8...202a) for asset transfer.
32
40
182
@CoinDesk
CoinDesk
29 days
⚡️ Consensus Hong Kong 2025 wasn't just a conference. It was a hackathon, a festival, a networking hub, and a deal-making powerhouse all into one. Now that you’ve seen the energy, would you like to join 15,000+ attendees? Get your ticket to be part of the action in 2026. NOW.
19
37
238
@PeckShieldAlert
PeckShieldAlert
4 months
#PeckShieldAlert @btcturk has been hacked, w/ estimated losses of ~$49M
@peckshield
PeckShield Inc.
4 months
Hi @btcturk, you may want to take a look: https://t.co/LOVhHNYUrI
10
23
102
@peckshield
PeckShield Inc.
4 months
Hi @btcturk, you may want to take a look: https://t.co/LOVhHNYUrI
22
20
169
@peckshield
PeckShield Inc.
4 months
Today's @CrediX_fi hack is due to compromised admin account 0xF321683831Be16eeD74dfA58b02a37483cEC662e, which has a number of roles, including POOL_ADMIN, BRIDGE, ASSET_LISTING_ADMIN, EMERGENCY_ADMIN, and RISK_ADMIN. And the BRIDGE role is abused to drain/borrow pool assets
11
19
104
@peckshield
PeckShield Inc.
5 months
Just confirmed: the bug was indeed introduced in the fix for the $1M bounty issue -
7
2
41
@peckshield
PeckShield Inc.
5 months
The post-mortem analysis of GMX V1 Exploit on Arbitrum is out and we want to share our thoughts: 1) The entry point of the attack was at https://t.co/ZySqTYnrJQ, not #L764. 2) While the reentrancy is being utilized, the exploited bug shares the same nature of an earlier (2022)
5
27
134