Top issues
Problem
Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. URL paths provide additional information to a web service when making a request. They are an optional, but an important part of the URL, as they may define specific content or actions based on the data being passed. Some parameters they pass might be considered sensitive information. Since path components are not encrypted this might cause sensitive information to leak. This issue is raised for URL paths than might contain information that attackers can easily intercept. Examples of sensitive information fields include passwords and other similar parameters.Prevalence in npm community
1 packages
found in
Top 100
9 packages
found in
Top 1k
124 packages
found in
Top 10k
28080 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
Operating systems allow multiple user accounts to coexist on a single computer system. Each registered user has identity information associated with their account. At the very least, user accounts consist of a user name and an optional password. In some cases, user account data may also include personally identifiable information. Extended personal information may include user's given and last name, their email and mailing address, personal photo and their telephone number. Financially motivated attackers may seek to collect personal information for purposes of selling the private data to a third-party. Malicious code that typically exhibits these behavior traits is commonly referred to as an information stealer. While the presence of code that accesses identity information does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Accessing identity information is a very common behavior for software packages. One example of acceptable use for such functions is verifying that the active user has purchased a software license that allows them to run the application.Prevalence in npm community
2 packages
found in
Top 100
6 packages
found in
Top 1k
166 packages
found in
Top 10k
34671 packages
in community
Next steps
Investigate reported detections as indicators of software tampering.
Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.
Top behaviors
Might contain potentially obfuscated code or data.
anomaly
Prevalence in npm community
Behavior often found in this community (Common)
21 packages
found in
Top 100
136 packages
found in
Top 1k
1248 packages
found in
Top 10k
390529 packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
7 packages
found in
Top 100
61 packages
found in
Top 1k
956 packages
found in
Top 10k
319930 packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in npm community
Behavior often found in this community (Common)
6 packages
found in
Top 100
44 packages
found in
Top 1k
657 packages
found in
Top 10k
175209 packages
in community
Encodes data using the Base16 algorithm.
file
Prevalence in npm community
Behavior often found in this community (Common)
15 packages
found in
Top 100
90 packages
found in
Top 1k
1202 packages
found in
Top 10k
290629 packages
in community
Executes files during installation or upon launch.
execution
Prevalence in npm community
No behavior prevalence information at this timeTop vulnerabilities
No vulnerabilities found.