Publishing an npm Github package only works for some organizations that I own - npm-publish

Question

I've been trying to publish a new npm package to my github organization nkemtasoft-react but it keeps failing with a 400 error status code with no message.
Oddly, when I try to publish the same package to one of my other organization backbuk using the same github token I used for nkemtasoft-react, it works.
In trying to figure out what was going on, I made a GET request directly to the npm api https://npm.pkg.github.com/#backbuk/mypackage providing my github PAT as a bearer token to see if I could get the details of mypackage and it returned the details of mypackage.
When I replace mypackage in the url with a non existing package so that the new url becomes https://npm.pkg.github.com/#backbuk/non-existing-module, it returned a 404 error as expected with the descriptive message:
{"error":"npm package \"non-existing-module\" does not exist under owner \"backbuk\""}
However, when I replace the owner from backbuk to nkemtasoft-react (which is still my organization) so that the new url becomes https://npm.pkg.github.com/#nkemtasoft-react/non-existing-module, I was expecting the same 404 error and message as above, but rather, it just throws a 400 error with no message.
Not sure what is going on and I'll be happy to provide more details to get the issue resolved. Thanks.