Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@socialgorithm/tournament-server
Advanced tools
Game-agnostic tournament server
An online version of this server is always running at server.socialgorithm.org, deployed using DigitalOcean.
To run locally:
$ npx @socialgorithm/tournament-server -h
tournament-server v10.0.0
Socialgorithm Tournament Server
Options
...
Clone the repo locally and run npm install
. Once dependencies are installed you can run:
$ npm run start:dev
This will run the typescript compiler and start the server, restarting the server whenever a file changes.
The server uses the debug
library to aid debugging. Simply run:
DEBUG=sg:* npm run start:dev
This will enable verbose logging of Socialgorithm related messages (use *
to log everything).
FAQs
Socialgorithm Tournament Server
The npm package @socialgorithm/tournament-server receives a total of 2 weekly downloads. As such, @socialgorithm/tournament-server popularity was classified as not popular.
We found that @socialgorithm/tournament-server demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.