DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
HighOpen VSX1 affected version

lauracode.wrap-selected-code

lauracode.wrap-selected-code has 1 version on Open VSX flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed.

  • lauracode.wrap-selected-code@0.0.2

The incident that flagged it

High

GlassWorm sleeper extensions activate on Open VSX

Roughly 40 malicious VS Code extensions surfaced March 14-18, 2026: 20+ new extensions, ~20 previously dormant sleepers activated, plus 11 extensionPack droppers. The campaign hosts VSIX payloads on attacker-controlled GitHub releases to evade registry takedowns. Publishing accounts: laura6909, martina0094, chiara585, francesca898.

Versions named here: 0.0.2

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

lauracode.wrap-selected-code is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse Open VSX manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged Open VSX packages

Other packages in the same incident

If lauracode.wrap-selected-code is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.