Published 2017-8-3
Developmnent security concerns

Not scared yet? Read...

There are many attempts to hack others, to display ads, get data, earn money or just be evil and encrypt data without possible return point.

Be safe.

This post contains few recent breaches and few rules how to not become victim.

NodeJs npm repository malware

Be cautious which npm packages you install.

Recently, there was malware in npm package called crossenv. Maybe you already heard that package name, it's very popular - but the trick is official package is cross-env, so you can easily not type sign - and install malware.

Npm is now holding that package name:

But there might be many others.

To prevent possible issues, always verify that you are installing package from verified owners.

NodeJS security scan

To be more safe, you can integrate automated check which might find vulnerable dependencies.

It's called nsp.

After integration to your build process, if nsp find vulnerable dependency (or it's version), it will intermediately stop your build! ..and you will be forced to remove risky package.


Chrome extensions Hijacking

Extensions in Chrome are massively used. Did you ever thought that some of your extensions might contains some malicious code?

Answer might be yes, as already some popular extensions contained malware:

It's really hard to prevent these kind of attacks, but basic tip would be to not install many extensions which you not necessarily need - keep in mind that many extensions has access to whole websites you are browsing (Eg. internet banking, etc).

If you are developer, you need many extensions - many of those has access to whole content of websites. My advice is: Never use you browser for development (with dev extensions) for browsing web like email, bank, shops. Instead create different profile without dev extensions, or use another browser for general use.

I like to use Firefox for "safe browsing" & Chrome for development combination.

Electron critical flaw

In popular Electron (NodeJs) framework is (was) critical flaw. It affects all apps written for Electron - like Spotify, Slack, Skype (new), VSCode, Atom, and more.

It's being fixed by apps pretty quickly, but still it's something what might cause security concerns.

More detail here

Hardware vulnerabilities

Spectre. Meltdown!

Those were found after many years used processor architecture. Attacker might read/modify another application through special set of processor instructions.

This affects milions of computers using Intel and AMD architecture.

Generally there is no special way how to protect yourself :o only to rely on verified software and vendors hotfixes which were applied pretty "quickly".

Another general security tips

Https (SSL)

Use HTTPS everywhere.

If you are web developer, always use websites with valid SSL certificate. You can even get one for free from Let's encrypt.

Never trust websites without certificate.

Firefox even displays error note if website allows write text to fields, but website doesn't have certificate active.

Without SSL (https), you are sending data without any encryption, so potentially everyone can read you communication.

Two Step verification

Use two step verification whenever you can.

Most of services and websites already allow to setup two step verification with SMS, or Google Authenticator (or other similar).

Note that Google Authenticator is much safer than SMS. Once you setup new website, it's working completely offline. While SMS can be more easily "catch" - by sniffing GSM network, or with applications in your phone.


Never underestimate attackers, whenever you are on Mac, Windows or Linux, there are always people who want's your computer power or your data.

And if you learned even single new security tip from this article I will be happy! If you already know all, that's even better.