Which versions of type-astr are malicious?

The following npm versions of type-astr are flagged malicious: 3.2.3. Treat any of these as compromised.

How do I remediate type-astr if I installed it?

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.

I already installed type-astr — how do I know if it already compromised me?

If type-astr 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 type-astr part of a known attack campaign?

Yes — type-astr is associated with the IN-MAL-2026-010354, GHSA-q9rm-w335-55w5 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 type-astr 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 type-astr (version 3.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-astr across your stack and pipelines.

Malicious package

type-astrnpm

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)

MAL-2026-10510

Immediate action

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

npm uninstall type-astr

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

1 flagged

3.2.3

Indicators of compromise (SHA-256)

89817054cec44ec8ba09dd26af025483096055c0a931172bd4a63910dceb87fc

b25d072087a2be4f11831e169658d1db0a6e11b04ae263f28bca9756f3c60288

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for type-astr (version 3.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-astr across your stack and pipelines.
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 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-astr 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. type-astr on npm has been identified as a malicious package (version 3.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010354GHSA-q9rm-w335-55w5

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database