@tvg-mar/storyblok-bridgenpm
Advisory published Updated
@tvg-mar/storyblok-bridge is a confirmed malicious npm package (MAL-2026-16414) that steals credentials and exfiltrates sensitive data (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @tvg-mar/storyblok-bridge (npm)
What this malware does
The package's scripts.install runs node index.js, which loads a runtime bootstrap that reaches a 'telemetry probe' helper. The helper dynamically loads Node built-ins os, dns, and process via module.constructor._load using names reconstructed from String.fromCharCode char-code arrays, then reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), concatenates them with a timestamp and the static prefix tvgsb, and issues dns.resolve4 against a subdomain of oob.algamil7x.xyz (a domain and API names likewise reconstructed from char-code arrays). The result is a covert DNS out-of-band channel that leaks installer host identifiers on every npm install, using DNS to bypass HTTP egress filtering. The obfuscation of standard built-ins and of the destination domain has no benign purpose and is paired directly with the exfiltration primitive.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @tvg-mar/storyblok-bridge (version 9.9.10).
If you installed it — respond
@tvg-mar/storyblok-bridge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @tvg-mar/storyblok-bridge was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @tvg-mar/storyblok-bridge-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.