https://github.com/byt3n33dl3/corporalkraken

Docker Payloads (Bypass) Data at the endpoint when running NestJS APK.

https://github.com/byt3n33dl3/corporalkraken

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (9.8%) to scientific vocabulary

Keywords

backdoor command docker payload shellscript
Last synced: 5 months ago · JSON representation

Repository

Docker Payloads (Bypass) Data at the endpoint when running NestJS APK.

Basic Info
  • Host: GitHub
  • Owner: byt3n33dl3
  • License: mit
  • Language: Dockerfile
  • Default Branch: main
  • Homepage:
  • Size: 149 KB
Statistics
  • Stars: 17
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Topics
backdoor command docker payload shellscript
Created over 1 year ago · Last pushed over 1 year ago
Metadata Files
Readme License

README.md

Malicious Docker Payload

This docker image is intended to emulate malicious behavior to test EDR/Anti Virus solutions on Docker/Kubernetes Hosts/Clusters.

How To Run

git clone https://github.com/pxcs/Payload_Docker && cd Payload_Docker docker build -t Payload_Docker:latest . docker run Payload_Docker:latest

What Tests are Running?

Anti Virus

EICAR Malware Sample

Network Endpoint Protection

Flightsim Malicious Network Sample


  • Defensive explaination ## How Malware Scanner Service works

This repository contains the code to build a pipeline that scans objects uploaded to GCS for malware, moving the documents to a clean or quarantined bucket depending on the malware scan status.

It illustrates how to use Cloud Run and Eventarc to build such a pipeline.

Architecture diagram

Example

Use the tutorial to understand how to configure your Google Cloud Platform project to use Cloud Run and Eventarc.

Using Environment variables in the configuration

The tutorial above uses a configuration file config.json built into the Docker container for the configuration of the unscanned, clean, quarantined and CVD updater cloud storage buckets.

Environment variables can be used to vary the deployment in 2 ways:

Expansion of environment variables

Any environment variables specified using shell-format within the config.json file will be expanded using envsubst.

Passing entire configuration as environment variable

An alternative to building the configuration file into the container is to use environmental variables to contain the configuration of the service, so that multiple deployments can use the same container, and configuration updates do not need a container rebuild.

This can be done by setting the environmental variable CONFIG_JSON containing the JSON configuration, which will override any config in the config.json file.

If using the gcloud run deploy command line, this environment variable must be set using the --env-vars-file argument, specifying a YAML file containing the environment variable definitions (This is because the commas in JSON would break the parsing of --set-env-vars)

Take care when embedding JSON in YAML - it is recommended to use the Literal Block Scalar style using |, as this preserves newlines and quotes

Big Thanks to googlecloud for explaination

Owner

  • Name: Sulaiman
  • Login: byt3n33dl3
  • Kind: user
  • Location: Error 403: Not on earth

I N F R A X 8 6

GitHub Events

Total
  • Watch event: 2
Last Year
  • Watch event: 2

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels

Dependencies

src/Dockerfile docker
  • golang alpine build