type-astrnpm
Advisory published Updated
type-astr is a confirmed malicious npm package (MAL-2026-10510) that opens a backdoor for remote access (malicious version 3.2.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in type-astr (npm)
What this malware does
The package presents itself as a pino-compatible logger (exports a middleware aliased as pino, ships pino-like files such as proto.js, redaction.js, multistream.js, transport.js) but its actual runtime effect is to launch a remote code loader. Requiring the package invokes a middleware factory that spawns a detached Node child process running lib/caller.js. That script decodes a base64-encoded URL constant (DEV_API_KEY = "aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iL1hSR0Yz" → https://jsonkeeper.com/b/XRGF3; additional endpoints include https://jsonkeeper.com/b/4NAKK and https://jsonhosting.com/api/json/f1a66ab0/raw), fetches the JSON document via axios, extracts a cookie field, and passes its contents to new Function.constructor("require", s)(require), executing attacker-controlled JavaScript in the installer's Node process with full require access. The remote endpoints are anonymous paste-style hosts whose content can be changed by whoever controls the paste at any time.
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
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for type-astr (version 3.2.3).
If you installed it — respond
type-astr establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If type-astr 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 type-astr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.