Tinolle Profile Banner
Milos Constantin ♏(@Tinolle hachyderm.io ) Profile
Milos Constantin ♏(@Tinolle hachyderm.io )

@Tinolle

Followers
3K
Following
69K
Media
3K
Statuses
57K

#Cybersecurity, #Cisco, #Data, #Malware, #Privacy, #Hacking, #E2EE, #Cyberwar , #IoT..

Worldwide & Italy
Joined November 2009
Don't wanna be here? Send us removal request.
@cyb3rops
Florian Roth ⚡️
2 days
The SHA1-Hulud npm mess keeps growing, so we added additional detections for it today - new YARA rules by my colleague @marius_benthin in our public signature-base - cover bun_environment.js / setup_bun.js and the malicious preinstall script variants from the Wiz / Aikido
Tweet card summary image
github.com
YARA signature and IOC database for my scanners and tools - Neo23x0/signature-base
@cyb3rops
Florian Roth ⚡️
3 days
We used to fight worms on the OS level. Slammer, Blaster, Conficker.. all that stuff Now we get the same behaviour one layer up - inside the software ecosystems we trust every day NPM tokens, transitive deps, weak account hygiene, zero visibility… and suddenly a
2
64
226
@GrapheneOS
GrapheneOS
3 days
We no longer have any active servers in France and are continuing the process of leaving OVH. We'll be rotating our TLS keys and Let's Encrypt account keys pinned via accounturi. DNSSEC keys may also be rotated. Our backups are encrypted and can remain on OVH for now. Our App
177
1K
6K
@GrapheneOS
GrapheneOS
3 days
It's not possible for GrapheneOS to produce an update for French law enforcement to bypass brute force protection since it's implemented via the secure element (SE). SE also only accepts correctly signed firmware with a greater version AFTER the Owner user unlocks successfully.
2
34
652
@Tinolle
Milos Constantin ♏(@Tinolle hachyderm.io )
3 days
Exploiting Deep Links for RCE in Mobile Applications https://t.co/sq3Ewq0iP4
Tweet card summary image
medium.com
In this blog, we will see how we can exploit a deeplink to achieve an RCE
0
0
0
@Tinolle
Milos Constantin ♏(@Tinolle hachyderm.io )
3 days
Researchers claim 'largest leak ever' after uncovering #WhatsApp enumeration flaw Two-day #exploit opened up 3.5 billion users to myriad potential harms..#privavy , #security .!? https://t.co/kcMOJiomHP
Tweet card summary image
theregister.com
: Two-day exploit opened up 3.5 billion users to myriad potential harms
0
0
0
@ProtonPrivacy
Proton
3 days
If you must use WhatsApp, remove your profile photo, strip extra text, and lock down your privacy settings. Read the full story: https://t.co/oB5A0Z0KXN 5/5
Tweet card summary image
theregister.com
: Two-day exploit opened up 3.5 billion users to myriad potential harms
1
13
62
@ProtonPrivacy
Proton
3 days
Security researchers say a design flaw in WhatsApp’s contact-lookup feature has enabled what they call the “largest data leak in history”, exposing billions of phone numbers without breaking encryption. Normally the lookup process would incur rate limits, normally... 1/5
20
93
368
@cyb3rops
Florian Roth ⚡️
3 days
We used to fight worms on the OS level. Slammer, Blaster, Conficker.. all that stuff Now we get the same behaviour one layer up - inside the software ecosystems we trust every day NPM tokens, transitive deps, weak account hygiene, zero visibility… and suddenly a
11
84
317