"node" Error message after installing Catalina

Problem resolved.

In my case, it appeared that Catalina found software installed from AT&T to be troublesome. I had previously used AT&T as my ISP.

An AT&T app was installed. Deleting it did not solve the problem, but deleting the "AT&T" folder (and its contents) from Macintosh HD>Library>Application Support did the trick.

The conflict appeared come from files used by AT&T for its "Troubleshoot & Resolve" feature.

Lucid, read through the thread where someone mentions removing the ATT folder from files. It worked for mine and others. See below as well.

In my case, it appeared that Catalina found software installed from AT&T to be troublesome. I had previously used AT&T as my ISP.

An AT&T app was installed. Deleting it did not solve the problem, but deleting the "AT&T" folder (and its contents) from Macintosh HD>Library>Application Support did the trick.

The conflict appeared come from files used by AT&T for its "Troubleshoot & Resolve" feature."

I am no longer using AT&T products, so I ended up deleting the folder mentioned in the above post as well as any AT&T folder I could find. Problem solved...

Well, close, but it's not a 32-bit issue, but rather new Gatekeeper security requirements around identifying who created the application and verifying it hasn't been modified since.

The result is similar—you can't run the code—but if differs in timing and what is affected. (There are also ways around this issue, but not around 32-bit code). The key part that is common is, both are incompatibilities with Catalina.

32-bit apps just won't run at all. 64-bit systems have been around over over a decade now, and since 2011's Lion release, MacOS has only run on 64-bit hardware, so developers have had a long, long time to recompile their software for 64-bit.

By contrast, some aspects of the process and detailed requirements for getting the proper signatures were firmed up only within the past few months. In particular, the requirement for "notarization" means applications have to be submitted to Apple to be checked for security issues, via an automated system. That certification then becomes part of the shipped product.

So developers, at a minimum, have to have their product notarized and re-released. There are a number of other security-related requirements that may require they make additional changes at the last minute.

So 32-bit issues, the developer has been AWOL for the past decade. Gatekeeper issues, the developer may be scrambling to fix with all due haste, or have already fixed quite recently.

But not bad for an uninformed conclusion—similar enough for most purposes! The real solution, when available, is to get updated software from the developer.

PS: @half_time_report's approach of authorizing each 'node' is reasonable if you can't update and don't have any reason to suspect foul play. Especially when it is something that was there and working before Catalina.

I would grow increasingly suspicious of new entrants there as time goes by, however.

https://discussions.apple.com/thread/250718394?answerId=251444739022#251444739022

This was the source of my node problem. The ATT folder has an uninstall link but it didn't do anything. I located the offending files in Macintosh HD/Library/Application Support/ATT ... sent entire folder to trash which required password. It would be helpful if the error message would show the path to the offending file. That would give some guidance to source of the issue.

the reply below solved my issue as well:

"In my case, it appeared that Catalina found software installed from AT&T to be troublesome. I had previously used AT&T as my ISP.

An AT&T app was installed. Deleting it did not solve the problem, but deleting the "AT&T" folder (and its contents) from Macintosh HD>Library>Application Support did the trick.

The conflict appeared come from files used by AT&T for its "Troubleshoot & Resolve" feature."

I am no longer using AT&T products, so I ended up deleting the folder mentioned in the above post as well as any AT&T folder I could find. Problem solved...

I don’t know what the node issue is. I suspect that the most likely explanation is that these node apps are malware that Catalina is blocking.

Normally, Gatekeeper does just that. It is the “gatekeeper”. Once something is already installed, it is no longer checked. But XProtect is updated on a regular basis and checks everything as soon as it is launched.

I suggested using EtreCheck and someone else suggested MalwareBytes. Either one would confirm the origin of these node executables, but no one has tried them.

Node is a developer tool. Any developer using node probably already knows whether or not they have node installed. This thread is about people who don’t know what node is and why it isn’t running on Catalina.

You are correct that the Node installers are not notarized. The Node developers, like all identified Apple developers, received an e-mail from Apple over a year ago informing them of upcoming security changes that would affect them. Furthermore, notarization has been a popular topic of discussion in the developer Apple community since Catalina was first released to developers in June, and since Notarization was required for new developers in Mojave 10.14.6. Curious that Node developers seem completely ignorant of all of this.

I also found an ATT folder in Library/Application Support.

Just like Surgeon_user, deleting it immediately stopped the infernal error messages.

I used to be on AT&T Uverse, and, just like Surgeon, AT&T was my ISP until recently. I don't recall a macOS app from them, but deleting this folder solved the problem.

How in the world did your figure this out? I didn't get a single clue that ATT or AT&T had anything to do with the problem.

Thanks!! This was my problem as well. Had deleted the software long ago, but still had those files in Libarary. Once I trashed them, the error went away. THX

I resolved this issue with a "tier 2" customer support rep at Apple. All of my problems related to old, dangling ATT files dating back five years found in multiple locations. The rep said he helped other people with this problem, and theirs also were due to ATT files.

Exactly the same problem. Did a search for "NODE" and found quite a few folders. Deleted them made no difference. Then found the EXEC file deleted that problem solved. Thanks All!

Hi InchH,

Thank you for using the Apple Support Communities! It's my understanding that you're running into a "node" alert on your Mac, and when you attempt to move the item to Trash, it fails. I'd like to provide you guidance.

Please follow the steps found in this article, which can help when you are unable to delete a file: If you can't empty the Trash on your Mac - Apple Support.

Reach back out if you need continued support.

Regards.

I saw a similar error trying to install node with the latest PKG file downloaded from nodejs.org on OSX 10.15 Catalina.

• “node-v12.13.0.pkg” can’t be opened because Apple cannot check it for malicious software.

Then I saw this article recommending nvm as the best way to install node on a Mac:

• https://medium.com/@itsromiljain/the-best-way-to-install-node-js-npm-and-yarn-on-mac-osx-4d8a8544987a

This let me install nvm, npm, and node on Catalina without trouble.

As a related topic, I found the following article about avoiding "sudo npm" interesting.

• https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92

Perhaps you should try:

https://www.malwarebytes.com

free version should suffice..