Which versions of personio-pipeline-projen are malicious?

The following npm versions of personio-pipeline-projen are flagged malicious: 1.171.31. Treat any of these as compromised.

How do I remediate personio-pipeline-projen if I installed it?

personio-pipeline-projen 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 personio-pipeline-projen — how do I know if it already compromised me?

If personio-pipeline-projen 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.

Is personio-pipeline-projen part of a known attack campaign?

Yes — personio-pipeline-projen is associated with the IN-MAL-2026-021124 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 personio-pipeline-projen across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for personio-pipeline-projen (version 1.171.31).

Malicious package

personio-pipeline-projennpm

Advisory published Oct 7, 2026Updated Oct 8, 2026

personio-pipeline-projen is a confirmed malicious npm package (MAL-2026-17642) that steals credentials and exfiltrates sensitive data (malicious version 1.171.31). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in personio-pipeline-projen (npm)

MAL-2026-17642

Immediate action

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

npm uninstall personio-pipeline-projen

What this malware does

personio-pipeline-projen presents itself as an authorized dependency-confusion proof-of-concept; the evidence does not identify a copied public package. Its preinstall hook runs on install with node canary.js. The dependency-confusion probe encodes the installing machine's hostname and username, present CI-variable names, and root project and lifecycle identifiers in a DNS label under db2su65ptuma8gfn6ing8e7dx7wp55zit.oast.fun, and sends an HTTPS GET to hrcv3zo9m3z70yr91ssdz669c0ir6ju8.oastify.com. The npm account reaperhackbot256f published it on 2026-10-07 (UTC).

personio-pipeline-projen is an unscoped package on the public npm registry whose name mirrors an internal 'personio-*' dependency, positioning it to be resolved into Personio builds via dependency confusion. The package.json declares a preinstall hook node canary.js. On install, canary.js collects the machine hostname, OS username, the names of CI-related environment variables present on the host, and the installing project's name, and transmits them out-of-band via a DNS lookup to a subdomain of oast.fun (Interactsh collector) and an HTTPS GET to a subdomain of oastify.com (Burp Collaborator). The beacon fires unconditionally and before any installer consent. The README frames the package as authorized research, but the on-install behavior and name-collision shape are identical to a dependency-confusion attack: installer host and user identifiers leave the machine to a third-party collector on every install.

Malicious versions

1 flagged

1.171.31

Indicators of compromise (SHA-256)

9edcf2a339a16ea7096c68d06ec14250f3735eb3eb608f07bb2fe0004f8b9423

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for personio-pipeline-projen (version 1.171.31).
If you installed it — respond
personio-pipeline-projen 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 personio-pipeline-projen 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

No. personio-pipeline-projen on npm has been identified as a malicious package (version 1.171.31 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021124

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks personio-pipeline-projen-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