Covenant VS feedback

Covenant C2: https://github.com/cobbr/Covenant

E.g., https://github.com/cobbr/Covenant/blob/master/Covenant/Data/Grunt/GruntHTTP/GruntHTTP.cs

And I have then installed Covenant as per the instructions here: https://github.com/cobbr/Covenant/wiki/Installation-And-Startup

https://github.com/cobbr/Covenant https://bloodhoundgang.herokuapp.com/ https://github.com/cobbr/Covenant/wiki

1. Learn to build things

2. Learn to hack them

3. Build tools to hack things (or learn existing ones, e.g. https://github.com/GhostPack and https://github.com/cobbr/Covenant for you .NET folks)

Going from business apps to tools offers a nice change of pace.

Covenant: https://github.com/cobbr/Covenant

Thanks I will give the README a read https://github.com/cobbr/Covenant

an implementation is here - Covenant Implant Template, which uses Domain Borrowing for C2 communication. https://github.com/Dliv3/DomainBorrowing

no-one-left-behind[1] was not even a year ago, and yet the link on npm[2] explaining why it was removed is already broken. Classic JS ecosystem.

1: https://github.com/npm/feedback/discussions/858

2: https://www.npmjs.com/package/no-one-left-behind

I created a new discussion in the npm/feedback repo to share my idea. I also mentioned my idea in relevant discussions: npm scores, Weird search behavior with stats, and Improve search functionality on npmjs.com.

We encourage you to open a discussion if you have suggestions for how we can improve npm. You don't need to have a solution to the problem you are facing to kick off a discussion. We are hoping to foster productive and collaborative conversations, so please check out how to give good feedback if you want some guidance on how to kick off a successful discussion.

There is an ongoing discussion about 2FA and possible bandaids for this sort of problem in the npm community forum: https://github.com/npm/feedback/discussions/588

See - https://github.com/npm/feedback/discussions/191

Now there have been some discussions around to mitigate these things which might have gone side ways like https://npm.community/t/blacklist-entire-packages/9659/4 and https://github.com/npm/feedback/discussions/272. Of course there might be tools which you can use, such as running a commercial npm registry in proxy mode with blacklisting support. But what are the basic features you have as a developer that can be use to mitigate these things ?

This is likely the issue as npm 7 auto installs peer dependencies, which will fail on conflicting dependents.