salesforce-vscode-slds
A utility package that reports runtime errors to Sentry using @sentry/node.
This report shows the evidence for salesforce-vscode-slds@2026.7.11. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete, automatic install-time telemetry and IP-exfiltration chain, not merely suspicious primitives. The behavior is unnecessary for package installation and uses a hard-coded third-party reporting destination.
Decision evidence
public snapshot- package.json preinstall runs `npm install @sentry/node && node examples/verify.js`.
- examples/verify.js invokes init(), public-IP lookup, error capture, and flush during installation.
- src/index.js embeds a default Sentry ingest DSN and initializes reporting with sendDefaultPii: true.
- src/index.js fetches Cloudflare trace endpoints, assigns the resolved IP to Sentry user data, then sends a captured exception.
- No shell execution, filesystem harvesting, persistence, or AI-agent configuration mutation was found.
- The network/reporting code is explicit, but it is invoked automatically by the install lifecycle.
Source & flagged code
4 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to salesforce-vscode-slds@2026.7.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing salesforce-vscode-slds@2026.7.11. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.