Spectra Assure

failIncident: Malware

Scanned:

@nstudio/xplat

latest

removed

malicious

Research

Cross-platform (xplat) tools for Nx workspaces.

License: Permissive (MIT)

Published:

Visit GitHub

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

4 suspicious application behaviors

Malware

10 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (StepSecurity)

More info

malware

Reported By: Community (Semgrep)

More info

malware

Reported By: Community (GitHub Advisory)

More info

malware

Reported By: Community (Aikido)

More info

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

malware

Reported By: Community (Wiz)

More info

malware

Reported By: Community (Checkmarx)

More info

malware

Reported By: Community (Sonatype)

More info

removal

N/AReported By: Community

Popularity

381.96k

Recorded Downloads Since 2021

Contributors

Declared Dependencies

Dependents

Top issues

See all issues

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

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

19.1k 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.

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

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

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

Avoid using this software package.

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. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in npm community

5 packages

found in

Top 100

2 packages

found in

Top 1k

39 packages

found in

Top 10k

21.37k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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

10 packages

found in

Top 100

53 packages

found in

Top 1k

981 packages

found in

Top 10k

194.82k 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.

Problem

Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.

Prevalence in npm community

0 packages

found in

Top 100

7 packages

found in

Top 1k

71 packages

found in

Top 10k

18.42k 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.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

19 packages

found in

Top 10k

2.71k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

21 packages

found in

Top 10k

2.85k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

18 packages

found in

Top 10k

2.86k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

22 packages

found in

Top 100

136 packages

found in

Top 1k

1267 packages

found in

Top 10k

411.22k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

15 packages

found in

Top 10k

2.32k packages

in community

Top vulnerabilities

No vulnerabilities found.

FAQ for @nstudio/xplat

What is @nstudio/xplat?

Cross-platform (xplat) tools for Nx workspaces. For more information about this package, visit its homepage.

Is @nstudio/xplat malicious or is it safe to use?

The npm package @nstudio/xplat 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. 4 other issues and risky behaviors were found. 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. The package @nstudio/xplat had 4 incidents in versions published within 2 years prior to the latest.

Is @nstudio/xplat popular?

The npm package @nstudio/xplat is not widely used. It has 382K 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 @nstudio/xplat once it is in my app?

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

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

Popularity

381.96k

Recorded Downloads Since 2021

Contributors

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in npm community

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

19.1k 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.

Problem

Prevalence in npm community

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

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

Avoid using this software package.

Problem

Prevalence in npm community

5 packages

found in

Top 100

2 packages

found in

Top 1k

39 packages

found in

Top 10k

21.37k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in npm community

10 packages

found in

Top 100

53 packages

found in

Top 1k

981 packages

found in

Top 10k

194.82k 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.

Problem

Prevalence in npm community

0 packages

found in

Top 100

7 packages

found in

Top 1k

71 packages

found in

Top 10k

18.42k 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.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

19 packages

found in

Top 10k

2.71k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

21 packages

found in

Top 10k

2.85k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

18 packages

found in

Top 10k

2.86k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

22 packages

found in

Top 100

136 packages

found in

Top 1k

1267 packages

found in

Top 10k

411.22k packages

in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)

0 packages

found in

Top 100

0 packages

found in

Top 1k

15 packages

found in

Top 10k

2.32k packages

in community

Top vulnerabilities

No vulnerabilities found.

@nstudio/xplat

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 4 malicious incidents in versions published within 2 years prior to the latestLatest version with malware incident detected: 6 months agoVersion: 20.0.7

INCIDENTS FOR THIS VERSION:

Popularity

Top issues

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in npm community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in npm community

Next steps

TH17131Detected presence of files containing domains used for intercepting and inspecting HTTP requests.hunting

Problem

Prevalence in npm community

Next steps

Top behaviors

Enumerates an environment variable that holds an Amazon Web Services (AWS) session token.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) secret access key.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) access key.search

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) web identity token location.search

Prevalence in npm community

Top vulnerabilities

FAQ for @nstudio/xplat

What is @nstudio/xplat?

Is @nstudio/xplat malicious or is it safe to use?

Is @nstudio/xplat popular?

How do I secure @nstudio/xplat once it is in my app?

Did you know...

Popularity

Top issues

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in npm community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in npm community

Next steps

TH17131Detected presence of files containing domains used for intercepting and inspecting HTTP requests.hunting

Problem

Prevalence in npm community

Next steps

Top behaviors

Enumerates an environment variable that holds an Amazon Web Services (AWS) session token.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) secret access key.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) access key.search

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) web identity token location.search

Prevalence in npm community