Spectra Assure
Community
Docs
warningRisk: Tampering
Scanned: about 1 month ago

sdp-transform

latest
A simple parser/writer for the Session Description Protocol
License: Permissive (MIT)
Published: 11 months ago



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 suspicious application behaviors
Malware
No evidence of malware inclusion

Popularity

37.29M
Recorded Downloads Since 2021
Contributor
Declared Dependencies
328
Dependents

Top issues

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

7 packages
found in
Top 100
50 packages
found in
Top 1k
526 packages
found in
Top 10k
155756 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.

Top behaviors

Prevalence in npm community

No behavior prevalence information at this time

Prevalence in npm community

Behavior often found in this community (Common)
2 packages
found in
Top 100
4 packages
found in
Top 1k
85 packages
found in
Top 10k
18857 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
16 packages
found in
Top 100
80 packages
found in
Top 1k
1432 packages
found in
Top 10k
442524 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
3 packages
found in
Top 100
40 packages
found in
Top 1k
706 packages
found in
Top 10k
232710 packages
in community

Prevalence in npm community

No behavior prevalence information at this time

Top vulnerabilities

No vulnerabilities found.