Spectra Assure

failIncident: Malware

Scanned:

postmark-mcp

latest

malicious

Universal Postmark MCP server using official SDK

License: Permissive (MIT)

Published:

See on npm

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

2 malware-like behaviors found

Malware

4 supply chain attack artifacts

IMPORTANT: All versions of this package have been malicious

Latest malware incident detected:

Version: 1.0.18

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (Koi)

More info

malware

Reported By: Community (Snyk)

More info

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

18 packages

found in

Top 10k

14717 packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

Problem

Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

17 packages

found in

Top 10k

15236 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH15108

Detected presence of files with behaviors that match the infostealer malware profile.

Causes risk: malware-like behaviors found

hunting

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 exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

2 packages

found in

Top 10k

10214 packages

in community

Next steps

Investigate reported detections.

Investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

TH30105

Detected presence of software components that were recently published to the public package repository.

hunting

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 npm 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.

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

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 npm 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.

TH30112

Detected presence of software components without a declared source code repository.

hunting

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in npm 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.

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.

List of software quality issues with the number of affected components.

Policies

Info

Count

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

18 packages

found in

Top 10k

14717 packages

in community

Next steps

If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

17 packages

found in

Top 10k

15236 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH15108

Detected presence of files with behaviors that match the infostealer malware profile.

Causes risk: malware-like behaviors found

hunting

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

2 packages

found in

Top 10k

10214 packages

in community

Next steps

Investigate reported detections.

Investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

TH30105

Detected presence of software components that were recently published to the public package repository.

hunting

Problem

Prevalence in npm 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.

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

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 npm 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.

TH30112

Detected presence of software components without a declared source code repository.

hunting

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in npm 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.