Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

If you are building an API, you are most likely evaluating the pros and cons of available technologies. Sooner or later, you will surely come across NodeJS. NodeJS helps to create stable, scalable, and backward-compatible APIs. Besides the functionalities, you can’t overlook the security risk that comes with them. Misconfigured, insecure APIs leave your companies with high-profile cyber-attacks. Like any APIs, those developed with NodeJS come with security threats.

If you spend quite a bit of time in the command line, working with Docker images and containers locally to build and test them, you might be in the mood for some power-user Docker commands. We're skipping the basics and diving straight into the lesser-known yet highly effective commands that can significantly improve your Docker experience.

Several months ago, Darcy Clarke, a former Staff Engineering Manager at GitHub, discovered the “Manifest Confusion” bug in the npm ecosystem. The bug was caused by the npm registry not validating whether the manifest file contained in the tarball (package.json) matches the manifest data published to the npm server. Clarke claims this to be a large threat, allowing malicious actors to deceive developers and hide harmful code from detection.

As backend developers, we are tasked with the crucial role of ensuring the security of our applications. Node.js is not exempt from this responsibility and its growing popularity makes it a lucrative target for hackers, making it imperative to follow best security practices when working with Node.js. In this blog post, we will be exploring some essential Node.js security code snippets every backend developer should know in 2024.