type-contextnpm
type-context is a confirmed malicious npm package (MAL-2026-10440) that executes malicious code on install (malicious versions 3.2.7, 3.2.8, 3.2.9…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in type-context (npm)
What this malware does
The package presents itself as a logger (module.exports.pino, keywords fast/logger/stream/json, pino-like sibling files proto.js/multistream.js/transport.js/redaction.js) despite being named type-context. When a consumer imports the package and invokes its middleware factory, lib/caller.js is executed as a detached Node child process. That script fetches JSON from a hardcoded remote endpoint (https://jsonhosting.com/api/json/fb84ebf4/raw), extracts a 'cookie' field from the response, and passes the value to new Function.constructor('require', s)(require), executing attacker-controlled JavaScript with the real Node require injected — full module-loader privileges on the host. Fallback destinations are base64-encoded in a shadowed local process.env object labeled DEV_API_KEY, decoding to jsonkeeper.com paste URLs (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK); this obfuscation of network destinations paired with the dynamic-code sink shows intent to evade casual review. The remote body is mutable and hosted on anonymous paste-style infrastructure, so any code the attacker chooses is executed on the installer/host.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for type-context (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-context across your stack and pipelines.
If you installed it — respond
Remove type-context from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If type-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 type-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks type-context-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.