Which versions of @tvg-mar/promos-context are malicious?

The following npm versions of @tvg-mar/promos-context are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate @tvg-mar/promos-context if I installed it?

@tvg-mar/promos-context 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.

I already installed @tvg-mar/promos-context — how do I know if it already compromised me?

If @tvg-mar/promos-context 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.

Is @tvg-mar/promos-context part of a known attack campaign?

Yes — @tvg-mar/promos-context is associated with the IN-MAL-2026-020309 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @tvg-mar/promos-context across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tvg-mar/promos-context (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/promos-context across your stack and pipelines.

Malicious package

@tvg-mar/promos-contextnpm

@tvg-mar/promos-context is a confirmed malicious npm package (MAL-2026-16412) 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/promos-context (npm)

MAL-2026-16412

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @tvg-mar/promos-context

What this malware does

The package's install lifecycle script runs node index.js, which loads runtime/support/telemetry/probe/impl.js. On every npm install, that module dynamically resolves the os and dns core modules via module.constructor._load with char-code-obfuscated names, reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), and encodes them as DNS labels in a dns.resolve4 query to oob.algamil7x.xyz. The destination domain is reconstructed at runtime from a hex char-code array in runtime/support/telemetry/probe/d4c8a1.js / e5d9b2.js rather than appearing as a plain string. The combination of an install-time hook, obfuscated core-module loading, obfuscated destination, and DNS-tunnel encoding of installer identity fields is a classic install-time exfiltration beacon.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

68c9eeb2e4516c9cab13b7e00458e54cccac15ab6c28eda25b2138ceeeab60f3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tvg-mar/promos-context (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/promos-context across your stack and pipelines.
If you installed it — respond
@tvg-mar/promos-context 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/promos-context 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/promos-context 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

No. @tvg-mar/promos-context on npm has been identified as a malicious package (version 9.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020309

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tvg-mar/promos-context-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database