Spectra Assure
Community
failIncident: Removal
Scanned: 12 days ago

Dapper

latest
removed
Top 10k
A high performance micro-ORM supporting MariaDB, PostgreSQL, SQL Server, SQLite and more.
License: unknown
Published: about 2 months ago
Visit GitHub
See on PowerShell Gallery

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 debugging symbols found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
1 outdated toolchains detected

Threats

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

INCIDENTS FOR THIS VERSION:

removal
N/AReported By: Community

Popularity

425
Total Downloads
3
Contributors
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. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

No prevalence information at this time

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

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. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

1 packages
found in
Top 100
2 packages
found in
Top 1k
6 packages
found in
Top 10k
18 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed-source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.

Prevalence in PowerShell Gallery community

3 packages
found in
Top 100
29 packages
found in
Top 1k
130 packages
found in
Top 10k
237 packages
in community

Next steps

Private debug database files should not be embedded within executables, and you should remove them from the software package before releasing it.
The integrity verification of the embedded database files should not be done with insecure hashing algorithms. SHA1 and MD5 hashes should be deprecated throughout the application, and a more secure SHA256 algorithm should be used instead.

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. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

1 packages
found in
Top 100
4 packages
found in
Top 1k
5 packages
found in
Top 10k
20 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Debug databases are typically only used during software development. On Windows, they are usually files embedded into the executable (PDB), while on Linux, they're contained inside special executable sections. The databases contain private debug symbols that make it significantly easier to reverse-engineer a closed-source application. In some cases, having a debug database is equivalent to having access to the source code. Presence of debug databases could indicate that one or more software components have been built using a debug profile, instead of the release. Private debug databases can be embedded into software components by programming language tools.

Prevalence in PowerShell Gallery community

3 packages
found in
Top 100
38 packages
found in
Top 1k
174 packages
found in
Top 10k
331 packages
in community

Next steps

To remediate this issue and remove private debugging information, refer to your programming language toolchain documentation.

Top behaviors

See all behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6511 packages
found in
Top 10k
11.95k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
9 packages
found in
Top 100
210 packages
found in
Top 1k
1129 packages
found in
Top 10k
1.86k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
97 packages
found in
Top 100
694 packages
found in
Top 1k
4447 packages
found in
Top 10k
7.42k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
1 packages
found in
Top 100
68 packages
found in
Top 1k
429 packages
found in
Top 10k
705 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
15 packages
found in
Top 100
101 packages
found in
Top 1k
803 packages
found in
Top 10k
1.24k packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Dapper

What is Dapper?

A high performance micro-ORM supporting MariaDB, PostgreSQL, SQL Server, SQLite and more. For more information about this package, visit its homepage.

Is Dapper malicious or is it safe to use?

The PS Gallery package Dapper has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. 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.

Is Dapper popular?

The PS Gallery package Dapper ranks among the top 10000 projects in this community. It has 425 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 Dapper once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Dapper behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Dapper 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.