mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

795
active users

#npm

2 posts2 participants0 posts today
Replied in thread

@loar entonces habría que entrar a revisar el detalle de la config del servidor web. Yo uso un contenedor con nginx proxy manager y desde ahí configuro todos los redireccionamientos y certificados. Es lo más simple.

👉🏻 nginxproxymanager.com/

nginxproxymanager.comNginx Proxy ManagerDocker container and built in Web Application for managing Nginx proxy hosts with a simple, powerful interface, providing free SSL support via Let's Encrypt

Atomic and Exodus crypto wallets targeted in malicious npm campaign

A malicious npm package named pdf-to-office was discovered targeting cryptocurrency wallets. The package, posing as a PDF to Office converter, injects malicious code into locally installed Atomic and Exodus wallets. This attack modifies legitimate files to redirect crypto funds to the attacker's wallet. The campaign shows persistence, as removing the malicious package doesn't remove the injected code from the wallets. Multiple versions of both wallets were targeted, with the attackers adapting their code accordingly. This incident highlights the growing scope of software supply chain risks, particularly in the cryptocurrency industry, and emphasizes the need for improved monitoring of both source code repositories and locally deployed applications.

Pulse ID: 67fd41f7af4b02a0fd75fb69
Pulse Link: otx.alienvault.com/pulse/67fd4
Pulse Author: AlienVault
Created: 2025-04-14 17:12:23

Be advised, this data is unverified and should be considered preliminary. Always do further verification.

LevelBlue Open Threat ExchangeLevelBlue - Open Threat ExchangeLearn about the latest cyber threats. Research, collaborate, and share threat intelligence in real time. Protect yourself and the community against today's emerging threats.

Properly patching packages: persistently producing patches for published projects, particularly practically prevented by patch-package policy

How to use `patch-package` to modify NPM dependencies, for instance when you're distributing an executable and you want to patch something you rely upon, without relying upon `postinstall` scripts.

fed.brid.gy/r/https://www.jvt.

“slopsquatting, a new term for a surprisingly effective type of software supply chain attack that emerges when LLMs “hallucinate” package names that don’t actually exist. If you’ve ever seen an AI recommend a package and thought, “Wait, is that real?”—you’ve already encountered the foundation of the problem.

And now attackers are catching on.”

The Rise of Slopsquatting: How #AI Hallucinations Are Fueling... socket.dev/blog/slopsquatting- #npm #dev #infosec

Edit: more info: bleepingcomputer.com/news/secu

SocketThe Rise of Slopsquatting: How AI Hallucinations Are Fueling...Slopsquatting is a new supply chain threat where AI-assisted code generators recommend hallucinated packages that attackers register and weaponize.

Hoo boy am I tired of seeing messages in my browser's JavaScript from some deep transitive dependency of the app I work on, saying "We're about to remove support for <feature that a slightly less nested transitive dependency uses>, sucks to be you."

This whole developer ecosystem is a nightmare of endless compatibility problems, 90% of them trivially avoidable with a moment's thought.

#Node#NPM#React

Exactly when I needed it, it appeared to me: NPM's workspaces feature.

Workspaces is a generic term that refers to the set of features in the npm cli that provides support to managing multiple packages from your local file system from within a singular top-level, root package.

workspaces | npm Docs docs.npmjs.com/cli/v8/using-np

docs.npmjs.comworkspaces | npm DocsWorking with workspaces

It seems that while I was building my huge monorepo in good old JS5 #javascript I missed the #npm workspaces concept that emerged somewhere along those years.
Now that I hit the wall with #deno and a bunch of dependency-wise intertwined packages, I've learned about deno's workspace feature that is a reimplementation of npm's workspaces.
Ok, let me see if I can organize my code using workspace(s)...