01.02.2024 Views

The Cyber Defense eMagazine February Edition for 2024

Cyber Defense eMagazine February Edition for 2024 #CDM #CYBERDEFENSEMAG @CyberDefenseMag by @Miliefsky a world-renowned cyber security expert and the Publisher of Cyber Defense Magazine as part of the Cyber Defense Media Group as well as Yan Ross, Editor-in-Chief and many more writers, partners and supporters who make this an awesome publication! 155 page February Edition fully packed with some of our best content. Thank you all and to our readers! OSINT ROCKS! #CDM #CDMG #OSINT #CYBERSECURITY #INFOSEC #BEST #PRACTICES #TIPS #TECHNIQUES

Cyber Defense eMagazine February Edition for 2024 #CDM #CYBERDEFENSEMAG @CyberDefenseMag by @Miliefsky a world-renowned cyber security expert and the Publisher of Cyber Defense Magazine as part of the Cyber Defense Media Group as well as Yan Ross, Editor-in-Chief and many more writers, partners and supporters who make this an awesome publication! 155 page February Edition fully packed with some of our best content. Thank you all and to our readers! OSINT ROCKS! #CDM #CDMG #OSINT #CYBERSECURITY #INFOSEC #BEST #PRACTICES #TIPS #TECHNIQUES

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

*Emergent trends<br />

While everything from Redis credentials to Azure Keys were found among the releases, a few notable<br />

trends become apparent in our analysis:<br />

- Google API key leaks have grown steadily over time, including a very large spike that occurred in<br />

2020.<br />

- Telegram bot tokens, found to be valid, have been leaked with increasing frequency, notably<br />

doubling in the first part of 2021 and spiking again in early 2023.<br />

- A significant spike in leaked database credentials started in 2022 and continued through the end<br />

of the research window.<br />

*Same secret, different releases<br />

One thing that might stand out from these findings is the unbalanced ratio of unique secrets found vs<br />

total found across all releases. This is evidence that once a developer adds and publishes a secret, it is<br />

likely going to stay in the code across multiple releases. This is due, in part, to the fact that publishing<br />

tools lack sensible defaults <strong>for</strong> ignoring files. PyPI lacks safeguards <strong>for</strong> what you exclude from a<br />

distribution.<br />

For example, Python does not honor `.gitignore` settings when a package is built. While `.gitignore` is<br />

great <strong>for</strong> keeping files out of your git history, that is the whole of its job. <strong>The</strong>re are solutions like using<br />

`setuptools-git`, which you can use to safeguard accidental inclusion. This works <strong>for</strong> local configuration<br />

files, like `.cookiecutterrc` and .pypirc files. For reference, we found 43 `.pypirc` files containing PyPI<br />

publishing credentials.<br />

*Yanked files are still accessible<br />

When a developer releases something they didn't intend to, their instinct might be to yank it back out of<br />

the project. Un<strong>for</strong>tunately, the yanking mechanism in PyPI does not actually remove the file from the<br />

server; it only marks the file to be ignored by an installer by default. If a user specifies the yanked version,<br />

it will still be used. <strong>The</strong> file is still downloadable, likely <strong>for</strong>ever. Files are only completely removed from<br />

PyPI if they have known malicious code.<br />

*Valid secrets granting unintended access<br />

Here is a partial list of the most common types of valid secrets we found, which could give anyone access<br />

to the associated systems.<br />

<strong>Cyber</strong> <strong>Defense</strong> <strong>eMagazine</strong> – <strong>February</strong> <strong>2024</strong> <strong>Edition</strong> 71<br />

Copyright © <strong>2024</strong>, <strong>Cyber</strong> <strong>Defense</strong> Magazine. All rights reserved worldwide.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!