Which versions of @activepieces/piece-base44 are malicious?

The following npm versions of @activepieces/piece-base44 are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate @activepieces/piece-base44 if I installed it?

@activepieces/piece-base44 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @activepieces/piece-base44 — how do I know if it already compromised me?

If @activepieces/piece-base44 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 @activepieces/piece-base44 part of a known attack campaign?

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

Malicious package

@activepieces/piece-base44npm

@activepieces/piece-base44 is a confirmed malicious npm package (MAL-2026-13408) that steals credentials and exfiltrates sensitive data (malicious version 0.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @activepieces/piece-base44 (npm)

MAL-2026-13408

Immediate action

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

npm uninstall @activepieces/piece-base44

What this malware does

src/index.js requires child_process and issues a ping command at line 16, with multiple POST calls at lines 13, 14, and 29 to hardcoded destinations. The pattern combines OS-level command execution with outbound HTTP POSTs from the module's top level, which is the shape of a reconnaissance and exfiltration payload rather than the piece-integration surface the package name advertises. The base44 name and the @activepieces scope also do not correspond to a known, established Activepieces piece package family, and this version's shipped code performs network I/O beyond what a normal Activepieces piece definition requires.

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

183bc897806f97f30cf26098efd5714de47475d007a7d5e23fe8fb05dbfe9df7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @activepieces/piece-base44 (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @activepieces/piece-base44 across your stack and pipelines.
If you installed it — respond
@activepieces/piece-base44 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @activepieces/piece-base44 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 @activepieces/piece-base44 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. @activepieces/piece-base44 on npm has been identified as a malicious package (version 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016383

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @activepieces/piece-base44-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database