Top issues
Detected presence of files containing domains used for intercepting and inspecting HTTP requests.
hunting
Problem
Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.Prevalence in npm community
0 packages
found in
Top 100
6 packages
found in
Top 1k
64 packages
found in
Top 10k
16488 packages
in community
Next steps
Investigate reported detections.
If the software should not include these network references, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider removing all references to flagged network locations.
Problem
Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.Prevalence in npm community
0 packages
found in
Top 100
0 packages
found in
Top 1k
1 packages
found in
Top 10k
1375 packages
in community
Next steps
Investigate reported detections.
If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider rewriting the flagged code without using the marked behaviors.
Top behaviors
Executes files during installation or upon launch.
execution
Prevalence in npm community
No behavior prevalence information at this timeMight monitor keystrokes.
steal
Prevalence in npm community
Behavior often found in this community (Common)
9 packages
found in
Top 100
35 packages
found in
Top 1k
740 packages
found in
Top 10k
309128 packages
in community
Might communicate to server over HTTP using XMLHttpRequest.
network
Prevalence in npm community
Behavior often found in this community (Common)
3 packages
found in
Top 100
27 packages
found in
Top 1k
556 packages
found in
Top 10k
215515 packages
in community
Makes HTTP POST requests.
network
Prevalence in npm community
Behavior often found in this community (Common)
1 packages
found in
Top 100
13 packages
found in
Top 1k
199 packages
found in
Top 10k
116198 packages
in community
Makes HTTP GET requests.
network
Prevalence in npm community
Behavior often found in this community (Common)
9 packages
found in
Top 100
54 packages
found in
Top 1k
860 packages
found in
Top 10k
314957 packages
in community
Top vulnerabilities
No vulnerabilities found.