SkillTotal

Is @microsoft/teams.common safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js network egress

@microsoft/teams.common is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 1 risky construct are reported for review. It can: network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

@microsoft/teams.common 2.1.0

npm_package · npm:@microsoft/teams.common
LOW
0
/ 100 risk score
Snapshot · scanned Sep 27, 2026 · @microsoft/teams.common@2.1.0 · engine 0.53.0 / ruleset 60

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @microsoft/teams.common's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
network egress

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Network egress
Interaction & Communication / Direct Communication

Findings (1)

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

import { RawAxiosRequestHeaders, AxiosResponse, AxiosRequestConfig, AxiosInstance } from 'axios';
var axios = require('axios');
var axios__default = /*#__PURE__*/_interopDefault(axios);
return this.http.request(resolvedConfig);
return this.http.request(resolvedConfig);
return this.http.get(url, transportConfig);
return this.http.request(resolvedConfig);
if (headers instanceof axios.AxiosHeaders) {
if (headers instanceof axios.AxiosHeaders) {
import axios, { AxiosHeaders } from 'axios';
this.http = axios.create({
return this.http.request(resolvedConfig);
return this.http.request(resolvedConfig);
return this.http.get(url, transportConfig);
return this.http.request(resolvedConfig);
import { AxiosInterceptorOptions, InternalAxiosRequestConfig, AxiosResponse } from 'axios';
import { AxiosRequestConfig } from 'axios';

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →