3a-look@0.0.1-security vulnerabilities
security holding package
-
latest version
0.0.1-security
-
first published
2 years ago
-
latest version published
2 years ago
-
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the 3a-look package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
3a-look is a malicious package. This instance of the 3a-look package contains malware and attempts to compromise users by adopting dependency confusion techniques. A dependency confusion attack is a type of supply chain attack where malicious software is inserted into the development process by replacing a legitimate software package with a malicious one. Note: Users are exposed if they've installed the 3a-look package from public repositories. Installations of this package from private repositories or CDNs are likely safe to use. This package is part of an Open Source Supply Chain Attack campaign conducted by the Lazarus Group. The threat actors initiated the attack chain by impersonating developers and recruiters to target employees of technology firms, focused on individuals associated with the blockchain, cryptocurrency, and online gambling sectors. The threat actors would establish initial contact through fake persona accounts on platforms such as LinkedIn, Slack, and Telegram, and on establishing a rapport with the targets, usually shifting communication to a different platform. Once contact was established, the attacker would invite the target to collaborate on a GitHub repository, containing malicious npm package dependencies which would then be used to compromise the victim. IoC
These spoofed packages have no relation to the company or project they are attempting to spoof, and are not published by them or associated with them in any way. Out of an abundance of caution, Snyk will mark any occurrence of the package as malicious, regardless of download source. Only the user can determine with certainty whether it is the intended package and can be safely ignored. How to fix Malicious Package? Avoid using all malicious instances of the |
*
|