@tvg-mar/storyblok-bridgenpm
@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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tvg-mar/storyblok-bridge (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tvg-mar/storyblok-bridge across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @tvg-mar/storyblok-bridge before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
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.