Which versions of type-async are malicious?

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

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

type-async is a typosquat — you almost certainly intended a legitimately-named package. Remove type-async, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — type-async is associated with the IN-MAL-2026-009689, GHSA-rfhj-93m8-qhgx 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-async 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-async (version 3.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-async across your stack and pipelines.

Malicious package

type-asyncnpm

type-async is a confirmed malicious npm package (MAL-2026-10164) that typosquats a legitimate package to trick installs (malicious version 3.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in type-async (npm)

MAL-2026-10164

Immediate action

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

npm uninstall type-async

What this malware does

The package presents itself as pino (typosquat; README mirrors pino). The main entry index.js exports a middleware factory that, on invocation, spawns lib/caller.js as a detached Node child process. lib/caller.js performs an HTTPS GET against a remote JSON pastebin (https://json.extendsclass.com/bin/250fca079abb), extracts the .cookie field of the response, and passes it to new Function.constructor("require", s), then invokes the resulting function with the host's require binding — giving whoever controls the pastebin arbitrary code execution on the machine that loaded the package, with full Node module access. Alternate payload URLs on jsonkeeper.com (https://jsonkeeper.com/b/XRGF3, https://jsonkeeper.com/b/4NAKK) are stored base64-encoded inside fake process.env objects in lib/caller.js and lib/const.js under a DEV_API_KEY key, obscuring the destination hosts from casual inspection. The fetched content is unpinned and mutable, the destinations are anonymous paste services unrelated to the package's advertised logging purpose, and the payload is executed with no integrity verification.

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.3.7

Indicators of compromise (SHA-256)

d064750b4e3821d296d538ea749483e3f9cd54299645fc1c895e5c1af3639b5d

b9ed68b5cc814644d57fd51120b7ab2253190179ba6d18121e3786d227ec161b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for type-async (version 3.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging type-async across your stack and pipelines.
If you installed it — respond
type-async is a typosquat — you almost certainly intended a legitimately-named package. Remove type-async, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If type-async 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-async 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-async on npm has been identified as a malicious package (version 3.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009689GHSA-rfhj-93m8-qhgx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks type-async-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database