Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 2 days ago

Microsoft Terraform

Artifact:
latest
VS Code extension for developing with Terraform on Azure
License: Permissive (MIT)
Published: about 2 months ago
Publisher: ms-azuretools
Visit GitHub
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
2 weak copyleft linked components
Secrets
10 web service credentials found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
2 baseline mitigations missing

Threats

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

Popularity

1.15M
Total Installs
1
Contributor
22
Declared Dependencies
3
Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in Visual Studio Code community

67 packages
found in
Top 100
548 packages
found in
Top 1k
3078 packages
found in
Top 10k
17.39k packages
in community

Next steps

We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. To authenticate, web service users provide a unique account identifier and a secret that confirms their access rights. Account access credentials are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

Prevalence in Visual Studio Code community

3 packages
found in
Top 100
32 packages
found in
Top 1k
49 packages
found in
Top 10k
257 packages
in community

Next steps

You should securely store web service access credentials, and fully automate their management and periodic rotation.
If credentials were published unintentionally and the software has been made public, you should revoke exposed credentials and file a security incident.
Examples of service credentials that may have been detected include AWS, Square, Zoho, Duo, PayPal and others.

Problem

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, web service users provide a unique token that confirms their access rights. These tokens are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

Prevalence in Visual Studio Code community

3 packages
found in
Top 100
34 packages
found in
Top 1k
71 packages
found in
Top 10k
457 packages
in community

Next steps

You should securely store web service access tokens, and fully automate their management and periodic rotation.
If tokens were published unintentionally and the software has been made public, you should revoke exposed tokens and file a security incident.
Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.

Problem

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Imported function addresses are pointers to the symbols that implement the application-required functionality. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.

Prevalence in Visual Studio Code community

20 packages
found in
Top 100
161 packages
found in
Top 1k
472 packages
found in
Top 10k
1.89k packages
in community

Next steps

Review the programming language linker options, and consider a build toolchain update.

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in Visual Studio Code community

68 packages
found in
Top 100
555 packages
found in
Top 1k
3086 packages
found in
Top 10k
17.47k packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
26 packages
found in
Top 100
136 packages
found in
Top 1k
330 packages
found in
Top 10k
1.5k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
67 packages
found in
Top 100
547 packages
found in
Top 1k
2891 packages
found in
Top 10k
14.99k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
75 packages
found in
Top 100
584 packages
found in
Top 1k
2965 packages
found in
Top 10k
15.79k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
74 packages
found in
Top 100
549 packages
found in
Top 1k
2492 packages
found in
Top 10k
11.96k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
32 packages
found in
Top 100
173 packages
found in
Top 1k
424 packages
found in
Top 10k
1.58k packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(5 Active Vulnerabilities)
4 (4 Fixable)
CVE-2025-68156h
CVE-2025-47907h
CVE-2025-47906m
1 (1 Fixable)
CVE-2025-65945h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Microsoft Terraform

What is Microsoft Terraform?

VS Code extension for developing with Terraform on Azure. For more information about this package, visit its homepage.

Is Microsoft Terraform malicious or is it safe to use?

The VS Code package Microsoft Terraform 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 downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is Microsoft Terraform popular?

The VS Code package Microsoft Terraform ranks among the top 1000 projects in this community. It has 1M 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 Microsoft Terraform once it is in my app?

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