If one purchases a machine and software that has no EULA, etc, can said person legally alter the code of the program purchased? So say myself or a company sells a printer, and as part of that printer package you have an add-on to purchase software with it. The customer purchases the machine and software and accepts terms you have laid out on the site, but that doesn't outline use, rights, or licensing of the software purchased as an add-on with the machine. There is no EULA to accept when running or using the software, and no terms outlined on the website, within the software, or anywhere for the purchaser or end user. So no agreement, no EULA, no restrictions or anything outline for use of the program purchased. Do they own the software? Can they legally alter the code of the program they purchased? Can they legally redistribute it or transfer ownership? Can they legally modify the code of the program for others who have also purchased the same package? Can they take that software and install it on a secondary machine?
Recall the basic principle of copyright law, as detailed in 17 USC 106: The copyright holder has the exclusive right to make copies; prepare derivative works; or distribute copies by sale, rental, lease, or lending. Other people can legally do these things only if they are given permission by the copyright holder, typically via a license. (Remember, the literal meaning of the word license is permission.) Often, the copyright holder will require a prospective licensee to accept various terms and conditions before the license will be granted. If there is &quot;no EULA&quot;, or if there is one but the purchaser has not agreed to its terms, then the purchaser has not been granted any such license, hence does not have permission to do any of the things listed above. If they do so anyway, it is illegal copyright infringement and they will be liable for damages. To use a firewall analogy, copyright law is &quot;default deny&quot;. So let's take your questions one by one: Do they own the software? US law has no concept of literally owning software. The closest thing is owning the copyright, which the purchaser certainly does not. It still belongs to the vendor that wrote the software (or whoever they may have later transferred it to). Can they legally alter the code of the program they purchased? No, that would be preparing a derivative work. The copyright holder has not granted them a license to do that. (There are some exceptions for purposes such as reverse engineering and interoperability, see 17 USC 1201(f)). Can they legally redistribute it No; again, that is the exclusive right of the copyright holder, and the purchaser has not received their permission. or transfer ownership? Maybe, if the first sale doctrine applies. Its application to software is complicated. The user has a better case for being able to sell the software if it exists as some tangible object which is transferred (physical media, pre-installed on hardware, etc). Can they legally modify the code of the program for others who have also purchased the same package? No, that would be preparing a derivative work. Can they take that software and install it on a secondary machine? No, that would be making a copy.
The exact laws will vary by region and country, but the laws will range anywhere between illegal and almost illegal. If you want to operate as legal as possible then you will have to disclose to the buyer that the software is malware or a crypter and you should require for the buyer to sign an agreement to only use the software for legal and educational purposes. Hiding the disclosure in a long Terms of Service agreement will likely not be sufficient. You will have to explicitly advertise that the software is malware and a crypter and that you are looking for reputable tech firms to buy your software in order to improve their software. If you sell software without disclosing to the customer that the software contains malware or a crypter then you are exposing yourself to a lawsuit for products liability, invasion of privacy, fraud and misrepresentation, the cost of damages, and possibly criminal liability.
Using it without permission is copyright infringement and illegal. Legally, you can try offering money to the company for the copyright or for a suitable license. For example offer them $1000 for a copy of the code licensed under the GPL license. If they accept, you are fine.
The CEO wants to "fool" users You are essentially admitting that the company you are working for is about to deceit its customers and asking whether that is legal. The relevant set of laws is rather sparse and does not give direct answers in regards to oAuth tokens or other details of that level (which is probably making your CEO think he can "handle" the arising questions). Probably the most relevant bit of legislation that applies here is The Federal Trade Commission Act (15 U.S.C. §§41-58) which prohibits unfair or deceptive practices and has been applied to online privacy and data security policies. I am pretty sure that, in practice, if the users take your company to court, it will be held liable because: users are allowing us to read their CRM data and once we get the data, the data become ours, and we can do whatever we want with it. Is this true? While the users are still allowing you to read their data it is completely up to the Terms/EULA what you can do with it. However, once you have made the users think that they have withdrawn your access (e.g. they "deleted" oAuth tokens), you are no longer authorized to read the current data (although the Terms may still allow you to use the old data you obtained when you had access). Silently continuing to access their data without their knowledge/approval is definitely a deceit. The CEO wants us to download all of their emails and store them in our database There would be nothing wrong with that if it was in the Terms. But if it is not, that would be a blatant (and easily punishable) breach of privacy. Note that you may also be held personally liable for this wrongdoing (if/when proved so). "Just doing your job" claim will not work.
It is certainly possible to transfer a copyright or other IP without an explicit charge, indeed it can be a pure gift, and normally would be when it is left by will, as is common enough. From a paid consultant it might be clearer to include a statement that the transfer is part of the consulting assignment, rather than putting a price of zero in a blank. But one could instead convey a permanent non-exclusive license, granting permission to use or modify the work in any way desired, ans saying that this is provided as part of the consulting process. Then there would be no question of what rights the consultant retained, or that the same or a very similar solution could be provided to different clients. Indeed such a license would not be so very different from a CC-BY license, or any of several open source licenses, although I would not use one of those by name. But the legal effect would be much the same, and the wording could be similar. Otherwise there could be a later claim that the right transferred precluded the consultant from using the same solution for other clients. Even if such a claim was not legally sound, and was not upheld, it could be a distraction and costly of time and energy at least.
Such clauses are called "copyright assignment", "invention assignment", and/or "works for hire" clauses, partly depending on the clause's intent and wording. They're pretty common in employment contracts for software development and some creative positions. Frankly, the clauses don't actually do much, at least in the US -- copyright law already recognizes the concept of works made for hire (which belong to the employer), and claims too far beyond that are often rejected if they aren't obviously related to company business. With that said, your hypothetical programmer's painting is safe unless it depicts, say, the contents of an email from the CEO. :) Even if the clause technically entitles the employer to claim ownership, the employer has no legitimate interest in doing so. Likewise, that app created outside work is safe as long as it is created using no company resources and is unrelated to the employer's business. If the app is obviously related, that's where things get hairy.
The EULA is in most jurisdictions a legally binding contract; there is plenty of case law that supports this. You can only be liable under a contract for breaching its terms and only to the extent that the other party suffers harm from that breach. Clearly, if you haven't read the terms then you are greatly increasing the chance that you will inadvertently breach them but not reading them would not, of itself, be a breach and I can't see what harm could flow anyway.
You are absolutely allowed to discuss or describe or criticizes software (or books or other copyrighted or trademarked things) without any permission from the copyright holder or trademark holder. This includes teaching people how to use those things. You may not, however, copy protected software without permission. For example you could not include a CD with a copy of Windows 10 as part of a course you taught on using Windows 10, without permission from Microsoft. Also, you may not use a trademark in such a way as to imply that your course is approved or endorsed by the trade mark holder, or by the maker of the trademarked item. If reasonable people could think that your Windows course was approved by Microsoft, you are probably infringing their trademark. Use of screenshots is more of a grey area. Such use, for purposes of teaching or of commentary, is probably covered by fair use (in the US) or fair dealing (in any of several other countries). But that is always a case-by-case determination, and depends on the exact facts, such as how extensive the use is, and whether it in any way harms the market for the original. If in doubt consulting a lawyer experienced in IP issues is wise. But aside from the issues of screenshots, the makers or copyright or trademark holders of software have no right to grant or withhold permission to one who teaches about the softrware, nor to demand any fee from any such person.