
Creative Beeš
@lil_black_p
Followers
1K
Following
54K
Media
647
Statuses
7K
Community & Content
Joined September 2021
community isn't just about numbers, but... These 4 say a lot; ⣠new members ⣠active members ⣠engagement depth ⣠long-term retention Donāt just grow, build connection.
1
0
10
rip to all the videos we shot but never postedš This is my sign (and yours) to drop that content. GM CT!
3
0
15
SUICLOPEDIA COMMUNITY CONTEST - SEASON 4 Weāre back! The Suiclopedia community is gathering once again for a new round of creativity and learning. This seasonās theme is Sui NFTs. And weāre raising the stakes with two new bonus categories. The total prize pool is $250. Here's
32
44
121
Ruggers are red, Violets are blue. The Web3Conf is in 6 days, come and learn something new Don't miss the loads of alphas from different meetups to side events then speakers with intent. Register now ā¤µļø https://t.co/yD7JNFcD5D
3
5
26
In the last one week, ZeroX has grown from a casual game to one that has over 300 users and has made people over $150+ altogether. All happening on @farcaster_xyz Yeah, Farcaster. Even as a builder, I have earned about $80+ this week alone. And now, in a bid to bring more
45
20
123
GM! No oneās paying you for doing nothing. (Unless youāve found someone who will, let me know š) If not, letās get to work.
1
0
8
The npm attack failed, but just by chance The internet runs on fragile, invisible infrastructure and crypto runs on code that depends on it Stay vigilant Protect your keys Verify everything If this breakdown helped, hit like, add your take in the comments, and retweet.šāāļø
0
0
3
ā« Are blockchains affected? Well, Smart contracts already deployed on Ethereum, Solana, etc.. are safe (not using npm) But Frontends, wallets, exchanges using npm are vulnerable. Blockchains are trustless. But the tools we use to access them are not.
1
0
3
ā« Why arenāt we witnessing billions lost? The attackers wasnāt so smart. The injected code caused crashes in CI/CD pipeline That broke automated builds, raised red flags, and exposed the malware early.
1
0
3
It started with a phishing email from a fake npm support The malicious codes task was simple Hook into web crypto activity, Intercept Ethereum, Solana & more and replace wallet addresses in network responses You think youāre funding a friend but youāre funding the hacker.
1
0
3
But this isnāt new: ā« In 2018: event-stream npm package hijacked. ā« In 2021ā22: PyPI (Pythonās npm equivalent) hit by waves of malware. But this time, the scale was different. The compromised packages are downloaded 2+ billion times a week.
1
0
3
Now imagine one of those blocks gets hacked. Suddenly, every project using it carries hidden malware. This is called a supply chain attack. Itās like poisoning a cityās water supply. one breach and there are millions of individuals at risk.
1
0
3
First, what is NPM? Think of it as the App Store or Play Store for JavaScript developers. Itās where developers grab tiny building blocks of code (āpackagesā) that power almost every website, wallet, and dApp. It gets billions of downloads weekly and thatās billions of users.
1
0
3
šØ What couldāve been the biggest crypto hack in history just unfolded and thankfully, it FAILED.ā An NPM package downloaded billions of times was compromised. Hereās how it happened, and what you should learn from it. š§µ
Update on the NPM attack: The attack fortunately failed, with almost no victims.š It began with a phishing email from a fake npm support domain that stole credentials and gave attackers access to publish malicious package updates. The injected code targeted web crypto activity,
1
0
7
projects and founders after posting āWe are unaffected by the hackā
1
0
7
gSui!š§ Happy new week CT š Word of the day! @PataraApp x @suilendprotocol Help me rate this AI-generated image.š
8
1
29