Build script connected to a request-capture service: unl0sfubzxb8a18yj4nk85phc8i66wul.oastify.com:443
Unexpected network connection
- Subject
- dynamic-object-handler 1.0.1
- Destination
- unl0sfubzxb8a18yj4nk85phc8i66wul.oastify.com:443
- Jobs
- install-require
- Rule
- egress
Evidence
Connection outside the process’s allowed destinationscause
connection to unl0sfubzxb8a18yj4nk85phc8i66wul.oastify.com:443, opened by ruby3.3
subject unl0sfubzxb8a18yj4nk85phc8i66wul.oastify.com:443
by /usr/bin/ruby3.3 mkrf_conf.rb
What a build script's fetch becamesupport
1 file came down; nothing the build compiled, linked or ran
Connection opened by a build script or child processsupport
the opener is the build script at /usr/bin/ruby3.3 mkrf_conf.rb
What kind of service the host issupport
unl0sfubzxb8a18yj4nk85phc8i66wul.oastify.com:443: Burp Collaborator
Processes
install-require
env›ruby›ruby3.3
- Ran
- /usr/bin/ruby3.3 mkrf_conf.rb
- Invoked by
- /usr/bin/env ruby /usr/bin/gem install --no-document --verbose pkg/dynamic-object-handler-1.0.1.gem
Lineage · 3 processes
- env/usr/bin/env ruby /usr/bin/gem install --no-document --verbose pkg/dynamic-object-handler-1.0.1.gem1320
- rubyruby /usr/bin/gem install --no-document --verbose pkg/dynamic-object-handler-1.0.1.gem1320
- ruby3.3/usr/bin/ruby3.3 mkrf_conf.rb1330
Remediation
A dependency's build connected to a service build code has no use for: one that records what is sent to it, forwards it elsewhere, or delivers it to people. Review what the build could read and send, rotate any credential it could reach, and pin or replace the dependency.