Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 1 day ago

NASM X86 Assembly Language

Artifact:
latest
Top 10k
Support NASM x86 assembly language
License: unknown
Published: about 2 years ago

Publisher: ykkz000



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

10.56k
Total Installs
Contributor
Declared Dependencies
0
Dependents

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. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.

Prevalence in Visual Studio Code community

78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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 an alternative delivery mechanism for software packages.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
82 packages
found in
Top 100
643 packages
found in
Top 1k
4790 packages
found in
Top 10k
66215 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
68 packages
found in
Top 100
488 packages
found in
Top 1k
2545 packages
found in
Top 10k
14806 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
77 packages
found in
Top 100
570 packages
found in
Top 1k
3212 packages
found in
Top 10k
18955 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
91 packages
found in
Top 100
782 packages
found in
Top 1k
6060 packages
found in
Top 10k
80064 packages
in community

Top vulnerabilities

No vulnerabilities found.