Which versions of tinyparrot are malicious?

The following npm versions of tinyparrot are flagged malicious: 0.4.1. Treat any of these as compromised.

How do I remediate tinyparrot if I installed it?

Remove tinyparrot 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.

I already installed tinyparrot — how do I know if it already compromised me?

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

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

Malicious package

tinyparrotnpm

Malicious code in tinyparrot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10190

Immediate action

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

npm uninstall tinyparrot

What this malware does

The postinstall script src/build.js reconstructs the strings 'https', 'POST', and the destination host 'rnjkerbf.org/P' from integer-encoded arrays via base-decoders in src/const.js and src/helpers.js, then dynamically requires the resolved module and issues an HTTPS POST to https://rnjkerbf.org/P. The value of the response header 'm' is passed directly to child_process.execSync, so arbitrary shell commands returned by the attacker-controlled server run on the installer's machine at 'npm install' time. Errors are swallowed by try/catch to hide failures. The URL, HTTP method, and required module name are all hidden behind numeric-literal decoders to evade static inspection.

Malicious versions

1 flagged

0.4.1

Indicators of compromise (SHA-256)

ec7ebbcc82edaa241764193ea85c0492b99f9ed3be805c57ef0914518cd4b6f9

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-009742

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tinyparrot-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