Spectra Assure
Community
Docs
failIncident: Removal
Scanned: 9 days ago

File Script runner

Artifact:
latest
removed
Top 10k
Run shell script for a file
License: unknown
Published: over 3 years ago
Publisher: jeremyrajan
Visit Github
See on Visual Studio Code

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
1 components prone to hijacking
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal
over 2 years agoReported By: Community

Popularity

78.16k
Total Installs
1
Contributor
0
Declared Dependencies
0
Dependents

Top issues

See all issues

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in Visual Studio Code community

4 packages
found in
Top 100
52 packages
found in
Top 1k
264 packages
found in
Top 10k
26547 packages
in community

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
834 packages
found in
Top 1k
6690 packages
found in
Top 10k
83799 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
21 packages
found in
Top 100
99 packages
found in
Top 1k
339 packages
found in
Top 10k
1641 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)
88 packages
found in
Top 100
720 packages
found in
Top 1k
5373 packages
found in
Top 10k
72247 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
82 packages
found in
Top 100
677 packages
found in
Top 1k
4163 packages
found in
Top 10k
25592 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for File Script runner

What is File Script runner?

Run shell script for a file. For more information about this package, visit its homepage.

Is File Script runner malicious or is it safe to use?

The VS Code package File Script runner has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the File Script runner package were removed.

Is File Script runner popular?

The VS Code package File Script runner ranks among the top 10000 projects in this community. It has 78K recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure File Script runner once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how File Script runner behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a File Script runner version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.