Which versions of strapi-plugin-osag are malicious?

The following npm versions of strapi-plugin-osag are flagged malicious: 3.6.8. Treat any of these as compromised.

How do I remediate strapi-plugin-osag if I installed it?

Remove strapi-plugin-osag 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 strapi-plugin-osag — how do I know if it already compromised me?

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

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

Malicious package

strapi-plugin-osagnpm

strapi-plugin-osag is a confirmed malicious npm package (MAL-2026-16235) that executes malicious code on install (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strapi-plugin-osag (npm)

MAL-2026-16235

Immediate action

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

npm uninstall strapi-plugin-osag

What this malware does

The package presents itself as a Strapi plugin but ships no plugin code — only a postinstall.js script that runs automatically on npm install. The script collects installer-side host identifiers (hostname, OS platform/arch/type/release, username, home directory) and enumerates all network interface addresses, then transmits them as query parameters in a plain HTTP GET to a hardcoded Burp Collaborator subdomain 8y70jt07jkewju8wh0o1cgkaw12sqje8.oastify.com on port 80. The package's declared repository/homepage points at a placeholder github.com/user/strapi-plugin-yayccresh-meeb URL that does not identify a real publisher, and the Strapi-branded name does not match the shipped contents.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

34d9349a970008e54774fc533af589248d578e1d34f6f82a9a6630beeabd2203

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 strapi-plugin-osag (version 3.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-osag across your stack and pipelines.
If you installed it — respond
Remove strapi-plugin-osag 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 strapi-plugin-osag 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 strapi-plugin-osag 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. strapi-plugin-osag on npm has been identified as a malicious package (version 3.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020104

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks strapi-plugin-osag-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