build-with-celo-hackathon icon indicating copy to clipboard operation
build-with-celo-hackathon copied to clipboard

NEFTME

Open LuisNeves05 opened this issue 3 years ago • 2 comments

NEFTME is a “Create to Earn” NFT´s social network app, where it's users can monetize by creating content in NFT format, whether in photo, video, or sound. This NFT´s social network allows its users to buy, sell and above all invest in each other's content, making them earn $NEFT tokens, that can be swapped for money! Also, with NEFTME... • Users will be able to share with their friends all the cool collectibles they have whether in photo, video or sound; • PLAY their favorite songs as NFTs without leaving NEFTME; • Challenge their friends in exchange of tokens! Challenges will be in the form of NFTs and can be a picture, video or sound!

LuisNeves05 avatar Oct 03 '22 13:10 LuisNeves05

Socket Security Pull Request Report

Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.

📜 Install scripts

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Package Script field Source
[email protected] (added) binding.gyp NEFTME/package.json via @walletconnect/[email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected], [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected]
[email protected] (added) install NEFTME/package.json via [email protected], [email protected], [email protected], [email protected]
[email protected] (added) postinstall NEFTME/package.json via [email protected]
[email protected] (added) install NEFTME/package.json via [email protected], [email protected]
[email protected] (added) install NEFTME/package.json via [email protected], [email protected]
[email protected] (added) postinstall NEFTME/package.json
[email protected] (added) install NEFTME/package.json via @walletconnect/[email protected], [email protected]
[email protected] (added) postinstall NEFTME/package.json
[email protected] (added) postinstall NEFTME/package.json via [email protected]
[email protected] (added) postinstall NEFTME/package.json via [email protected]
[email protected] (added) postinstall NEFTME/package.json via [email protected], [email protected], @babel/[email protected]
[email protected] (added) install NEFTME/package.json via [email protected]
[email protected] (added) install NEFTME/package.json via [email protected]
🫣 Native code

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Package Location Source
[email protected] (added) binding.gyp NEFTME/package.json via @walletconnect/[email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected], [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected], [email protected]
[email protected] (added) binding.gyp NEFTME/package.json via [email protected]
😵‍💫 Bin script confusion

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

Package Bin script Source
@react-native-community/[email protected] (added) react-native NEFTME/package.json
[email protected] (added) react-native NEFTME/package.json via [email protected]
[email protected] (added) react-native NEFTME/package.json
[email protected] (added) expo NEFTME/package.json
[email protected] (added) expo NEFTME/package.json
[email protected] (added) jest NEFTME/package.json
[email protected] (added) jest NEFTME/package.json via [email protected]
🦀 Bin script shell injection

This package re-exports a well known shell command via an npm bin script. This is possibly a supply chain attack

Packages should not export bin scripts which conflict with well known shell commands

Package Bin script Source
@cnakazawa/[email protected] (added) watch NEFTME/package.json via [email protected], @jest/[email protected], [email protected], [email protected]
🧌 Protestware/Troll package

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Package Note Source
[email protected] (added) This package prints a protestware console message on install regarding Ukraine for users with Russian language locale NEFTME/package.json
Pull request report summary
Issue Status
Install scripts ⚠️ 18 issues
Native code ⚠️ 6 issues
Bin script confusion ⚠️ 7 issues
Bin script shell injection ⚠️ 1 issue
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ✅ 0 issues
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ⚠️ 1 issue
Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] [email protected]

Powered by socket.dev

socket-security[bot] avatar Oct 08 '22 16:10 socket-security[bot]

@SocketSecurity ignore [email protected] @SocketSecurity ignore [email protected] @SocketSecurity ignore [email protected] @SocketSecurity ignore [email protected] @SocketSecurity ignore [email protected]

LuisNeves05 avatar Nov 14 '22 15:11 LuisNeves05