Search
1000 results for “0x0”
-
While investigating an infected website, we noticed call to BSC testnet contract 0x0967296defa0fd586c9ede5730380e2b059fab95 : https://testnet.bscscan.com/address/0x0967296defa0fd586c9ede5730380e2b059fab95
The contract’s content is clearly malicious and connects over WebSocket to suckerity[.]xyz (behind Cloudflare), not related to #ClearFake, but reminds us #Magecart related injections:
-
While investigating an infected website, we noticed call to BSC testnet contract 0x0967296defa0fd586c9ede5730380e2b059fab95 : https://testnet.bscscan.com/address/0x0967296defa0fd586c9ede5730380e2b059fab95
The contract’s content is clearly malicious and connects over WebSocket to suckerity[.]xyz (behind Cloudflare), not related to #ClearFake, but reminds us #Magecart related injections:
-
While investigating an infected website, we noticed call to BSC testnet contract 0x0967296defa0fd586c9ede5730380e2b059fab95 : https://testnet.bscscan.com/address/0x0967296defa0fd586c9ede5730380e2b059fab95
The contract’s content is clearly malicious and connects over WebSocket to suckerity[.]xyz (behind Cloudflare), not related to #ClearFake, but reminds us #Magecart related injections:
-
While investigating an infected website, we noticed call to BSC testnet contract 0x0967296defa0fd586c9ede5730380e2b059fab95 : https://testnet.bscscan.com/address/0x0967296defa0fd586c9ede5730380e2b059fab95
The contract’s content is clearly malicious and connects over WebSocket to suckerity[.]xyz (behind Cloudflare), not related to #ClearFake, but reminds us #Magecart related injections:
-
Gematik bei der Ausarbeitung des Sicherheitskonzepts der ePA.
#epa #gematik #ePatientenakte #epa_widerspruch https://infosec.exchange/@0x00string/113834049892028065
-
Thanks Joshua Bagley for collecting an edition of Origin 💫
https://www.artblocks.io/marketplace/asset/0x0000018afa7ca51648ed4b2b00c133005ea17115/31
-
Thanks Joshua Bagley for collecting an edition of Origin 💫
https://www.artblocks.io/marketplace/asset/0x0000018afa7ca51648ed4b2b00c133005ea17115/31
-
Sábado 28 de setembro de 2024, 18h vamos lançar a Tecniquim 0x01, nossa zine sobre arte e programação, lá no #GaroaHackerClube, querido #hackerspace de #SãoPaulo, estejam convidados!
-
Es ist soweit.
Die neuste #episode des #zeroday #podcast #0x0d ist mit episode #0d116 online.Dieses mal haben wir uns eine #expertin eingeladen mit dem wir uns über die #Sicherheit und den #Datenschutz von #Mastodon und dem #Fediverse unterhalten.
#Danke noch einmal an dieser Stelle an @blue1337blood für Ihre Zeit und Expertise
Wir wünschen euch viel Spass beim Hören und einen schönen Juli.
https://0x0d.de/2024/06/0d116-interview-fediverse-security-expertin/
-
Es ist soweit.
Die neuste #episode des #zeroday #podcast #0x0d ist mit episode #0d116 online.Dieses mal haben wir uns eine #expertin eingeladen mit dem wir uns über die #Sicherheit und den #Datenschutz von #Mastodon und dem #Fediverse unterhalten.
#Danke noch einmal an dieser Stelle an @blue1337blood für Ihre Zeit und Expertise
Wir wünschen euch viel Spass beim Hören und einen schönen Juli.
https://0x0d.de/2024/06/0d116-interview-fediverse-security-expertin/
-
Es ist soweit.
Die neuste #episode des #zeroday #podcast #0x0d ist mit episode #0d116 online.Dieses mal haben wir uns eine #expertin eingeladen mit dem wir uns über die #Sicherheit und den #Datenschutz von #Mastodon und dem #Fediverse unterhalten.
#Danke noch einmal an dieser Stelle an @blue1337blood für Ihre Zeit und Expertise
Wir wünschen euch viel Spass beim Hören und einen schönen Juli.
https://0x0d.de/2024/06/0d116-interview-fediverse-security-expertin/
-
Es ist soweit.
Die neuste #episode des #zeroday #podcast #0x0d ist mit episode #0d116 online.Dieses mal haben wir uns eine #expertin eingeladen mit dem wir uns über die #Sicherheit und den #Datenschutz von #Mastodon und dem #Fediverse unterhalten.
#Danke noch einmal an dieser Stelle an @blue1337blood für Ihre Zeit und Expertise
Wir wünschen euch viel Spass beim Hören und einen schönen Juli.
https://0x0d.de/2024/06/0d116-interview-fediverse-security-expertin/
-
Es ist soweit.
Die neuste #episode des #zeroday #podcast #0x0d ist mit episode #0d116 online.Dieses mal haben wir uns eine #expertin eingeladen mit dem wir uns über die #Sicherheit und den #Datenschutz von #Mastodon und dem #Fediverse unterhalten.
#Danke noch einmal an dieser Stelle an @blue1337blood für Ihre Zeit und Expertise
Wir wünschen euch viel Spass beim Hören und einen schönen Juli.
https://0x0d.de/2024/06/0d116-interview-fediverse-security-expertin/
-
🔊 #NowPlaying on BBCRadio2's #TheBluesShowWithCerysMatthews
Kitty Liv:
🎵 Keep Your Head Up Highhttps://open.spotify.com/track/2uHjpkk0X0kQeDE0kYGnq6
https://kittyliv.bandcamp.com/track/keep-your-head-up-high
#Bandcamp -
Phantom beauty.
Aurora Nightshade.https://opensea.io/assets/matic/0x00f693cd5bf8be5501643bdc15a1ce1e04cdacc6/1/
-
@HonkHase die sind ja echt in der Steinzeit liegen geblieben 1234 war das beliebteste passwort 1980 heute ist es 123456
#password #sicherheit #sicherheitslucken #0x0d #zeroday -
@helge For reference, in case it can help anyone else, putting a breakpoint in `init(0` and looking at the closest couple of stack frames, you'll see an entry like this:
#2 0x000000010063df94 in implicit closure #2 in implicit closure #1 in variable initialization expression of ReKeyApp._store ()
or
#2 0x0000000100631cdc in implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store ()
It very helpfully tells you the class (or struct) causing the instantiation.
Would be nice if #Xcode actually selected the line in the source instead of a line in a block of assembly, but the comments in that are helpful too:
ReKey`implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store:
0x100631cc0 <+0>: stp x20, x19, [sp, #-0x20]!
0x100631cc4 <+4>: stp x29, x30, [sp, #0x10]
0x100631cc8 <+8>: add x29, sp, #0x10
0x100631ccc <+12>: mov x0, #0x0
0x100631cd0 <+16>: bl 0x10062d700 ; type metadata accessor for ReKey.Store at <compiler-generated>
0x100631cd4 <+20>: mov x20, x0
0x100631cd8 <+24>: bl 0x100623770 ; ReKey.Store.__allocating_init() -> ReKey.Store at Store.swift:43
-> 0x100631cdc <+28>: ldp x29, x30, [sp, #0x10]
0x100631ce0 <+32>: ldp x20, x19, [sp], #0x20
0x100631ce4 <+36>: ret -
@helge For reference, in case it can help anyone else, putting a breakpoint in `init(0` and looking at the closest couple of stack frames, you'll see an entry like this:
#2 0x000000010063df94 in implicit closure #2 in implicit closure #1 in variable initialization expression of ReKeyApp._store ()
or
#2 0x0000000100631cdc in implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store ()
It very helpfully tells you the class (or struct) causing the instantiation.
Would be nice if #Xcode actually selected the line in the source instead of a line in a block of assembly, but the comments in that are helpful too:
ReKey`implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store:
0x100631cc0 <+0>: stp x20, x19, [sp, #-0x20]!
0x100631cc4 <+4>: stp x29, x30, [sp, #0x10]
0x100631cc8 <+8>: add x29, sp, #0x10
0x100631ccc <+12>: mov x0, #0x0
0x100631cd0 <+16>: bl 0x10062d700 ; type metadata accessor for ReKey.Store at <compiler-generated>
0x100631cd4 <+20>: mov x20, x0
0x100631cd8 <+24>: bl 0x100623770 ; ReKey.Store.__allocating_init() -> ReKey.Store at Store.swift:43
-> 0x100631cdc <+28>: ldp x29, x30, [sp, #0x10]
0x100631ce0 <+32>: ldp x20, x19, [sp], #0x20
0x100631ce4 <+36>: ret -
@helge For reference, in case it can help anyone else, putting a breakpoint in `init(0` and looking at the closest couple of stack frames, you'll see an entry like this:
#2 0x000000010063df94 in implicit closure #2 in implicit closure #1 in variable initialization expression of ReKeyApp._store ()
or
#2 0x0000000100631cdc in implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store ()
It very helpfully tells you the class (or struct) causing the instantiation.
Would be nice if #Xcode actually selected the line in the source instead of a line in a block of assembly, but the comments in that are helpful too:
ReKey`implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store:
0x100631cc0 <+0>: stp x20, x19, [sp, #-0x20]!
0x100631cc4 <+4>: stp x29, x30, [sp, #0x10]
0x100631cc8 <+8>: add x29, sp, #0x10
0x100631ccc <+12>: mov x0, #0x0
0x100631cd0 <+16>: bl 0x10062d700 ; type metadata accessor for ReKey.Store at <compiler-generated>
0x100631cd4 <+20>: mov x20, x0
0x100631cd8 <+24>: bl 0x100623770 ; ReKey.Store.__allocating_init() -> ReKey.Store at Store.swift:43
-> 0x100631cdc <+28>: ldp x29, x30, [sp, #0x10]
0x100631ce0 <+32>: ldp x20, x19, [sp], #0x20
0x100631ce4 <+36>: ret -
@helge For reference, in case it can help anyone else, putting a breakpoint in `init(0` and looking at the closest couple of stack frames, you'll see an entry like this:
#2 0x000000010063df94 in implicit closure #2 in implicit closure #1 in variable initialization expression of ReKeyApp._store ()
or
#2 0x0000000100631cdc in implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store ()
It very helpfully tells you the class (or struct) causing the instantiation.
Would be nice if #Xcode actually selected the line in the source instead of a line in a block of assembly, but the comments in that are helpful too:
ReKey`implicit closure #2 in implicit closure #1 in variable initialization expression of ContentView._store:
0x100631cc0 <+0>: stp x20, x19, [sp, #-0x20]!
0x100631cc4 <+4>: stp x29, x30, [sp, #0x10]
0x100631cc8 <+8>: add x29, sp, #0x10
0x100631ccc <+12>: mov x0, #0x0
0x100631cd0 <+16>: bl 0x10062d700 ; type metadata accessor for ReKey.Store at <compiler-generated>
0x100631cd4 <+20>: mov x20, x0
0x100631cd8 <+24>: bl 0x100623770 ; ReKey.Store.__allocating_init() -> ReKey.Store at Store.swift:43
-> 0x100631cdc <+28>: ldp x29, x30, [sp, #0x10]
0x100631ce0 <+32>: ldp x20, x19, [sp], #0x20
0x100631ce4 <+36>: ret -
Interesting Content-Types I have noticed in the 2023-07 mobile HTTP Archive crawl:
Content-Type: [*/*]
Content-Type: */*
Content-Type: #<Mime::NullType:0x0000000cf50828>
Content-Type: <content-typeheader>
Content-Type: <img/>
Content-Type: $MIMETYPE
Content-Type: 2
Content-Type: AddType font/woff
Content-Type: all/all
Content-Type: application/jason
Content-Type: application/jon
Content-Type: Default
Content-Type: FALSE
Content-Type: IMAGE -
🚀🎉 Genesis City Launch: Embark on the Ultimate Adventure in MintWorldGame! 🌟🎮
-
Die neue Episode ist online.
In Episode 0d106 teile ich ein paar Gedanken zu technischen Schulden mit Sven und bringe ihn gleichzeitig bei was technische Schulden sind.
Fälschlicherweise ziehe ich eine falsche Referenz zur Herkunft des Begriffs "Technische Schulden" aber Sven hat trotzdem was gelernt, womit das Ziel erreicht wurde. -
4) This giant pixel art piece Floor796, created by Russian artist 0x00. It's "an ever-expanding animation scene showing the life of the 796th floor of the huge space station" featuring hundreds of pop culture Easter eggs. (Be sure to check out the Russian-language interview linked in the "About" tab for the breakdown on how the animation renderer was created)
-
4) This giant pixel art piece Floor796, created by Russian artist 0x00. It's "an ever-expanding animation scene showing the life of the 796th floor of the huge space station" featuring hundreds of pop culture Easter eggs. (Be sure to check out the Russian-language interview linked in the "About" tab for the breakdown on how the animation renderer was created)
-
4) This giant pixel art piece Floor796, created by Russian artist 0x00. It's "an ever-expanding animation scene showing the life of the 796th floor of the huge space station" featuring hundreds of pop culture Easter eggs. (Be sure to check out the Russian-language interview linked in the "About" tab for the breakdown on how the animation renderer was created)
-
4) This giant pixel art piece Floor796, created by Russian artist 0x00. It's "an ever-expanding animation scene showing the life of the 796th floor of the huge space station" featuring hundreds of pop culture Easter eggs. (Be sure to check out the Russian-language interview linked in the "About" tab for the breakdown on how the animation renderer was created)